[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] building the Memory Browser and Traditional Renderer
|
John
The sequence of events for me
was
1.) Update all
code in my project space to HEAD ( I hade only made changes in
VariableVMNode and nothing else )
2.) Obtain M7 and
change to point to it ( was pointing to M6 ).
3.) Clean and
rebuild everything.
4.) Saw all of
these errors.
5.) reset defaults
for those two projects
6.) Errors went
away as expected.
7.) Applied Teodor
Madan changes 312098 ( which only changes the Memory Browser ). Works well by
the way. I really like it.
So yes this is a mystery. Tell you what,
please do not waste any time on this for now. Since
I had no changes of my own, I will delete
those projects and reload them from scratch from
HEAD. If I still see the issue then I'll
get in touch. Otherwise ( since you are not seeing these
errors in HEAD ) lets assume it is just my
environment for now until I can experiment.
Thanks
Randy
Randy, something isn't making sense. Are the errors you're seeing
possibly related to the new code you're trying to apply from Teo. I'm pretty
certain these issues aren't on HEAD; I checked out HEAD this morning and had no
such issues. If the issues are with the new code, then my changes to the project
are serving us well. It's pointing to things that should be correcting in the
new code before it's checked in. A commitment to zero-warning code goes beyond a
one-time cleanup. It means we're going to make sure the code stays clean of any
such warnings in the future. My changing of the project settings makes that a
requirement (what's the point of one person cleaning up warnings if someone else
is just going to be checking in more).
John
At 03:02 PM 5/10/2010,
Rohrbach, Randy wrote:
Content-Class:
urn:content-classes:message
Content-Type:
multipart/alternative;
boundary="----_=_NextPart_001_01CAF07B.B9632F8F"
hi John,
I
saw the email about the AbstractPane. But I am seeing more than just that
error ( 53 in all ).
They are listed below as an
example.
Is it
your intent to resolve the warnings by suppressing them or actually changing
the code where
possible to do it in some other way. In any
event please let me know when this is done.
For now though I am just going to change my
settings. I want to apply a couple of patches from
Teodor
Madan and I need to test them.
Thanks for the input.
Randy
Description Resource Path Location Type
Class is a raw type.
References to generic type Class<T> should be parameterized
MemoryBrowser.java
/org.eclipse.cdt.debug.ui.memory.memorybrowser/src/org/eclipse/cdt/debug/ui/memory/memorybrowser
line 606 Java Problem
Class is a raw type. References to generic type
Class<T> should be parameterized TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1196 Java Problem
Discouraged access: The constructor
GoToAddressComposite() is not accessible due to restriction on required
project org.eclipse.debug.ui Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 191 Java Problem
Discouraged access: The field
CopyViewToClipboardAction_title from the type DebugUIMessages is not
accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1288 Java Problem
Discouraged access: The field
CopyViewToClipboardAction_tooltip from the type DebugUIMessages is not
accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1289 Java Problem
Discouraged access: The field FONT_NAME from the
type IInternalDebugUIConstants is not accessible due to restriction on
required project org.eclipse.debug.ui Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 169 Java Problem
Discouraged access: The field FONT_NAME from the type
IInternalDebugUIConstants is not accessible due to restriction on required
project org.eclipse.debug.ui TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 107 Java Problem
Discouraged access: The field FONT_NAME from the type
IInternalDebugUIConstants is not accessible due to restriction on required
project org.eclipse.debug.ui TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 111 Java Problem
Discouraged access: The field
IMG_DLCL_COPY_VIEW_TO_CLIPBOARD from the type IInternalDebugUIConstants is not
accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1295 Java Problem
Discouraged access: The field
IMG_ELCL_COPY_VIEW_TO_CLIPBOARD from the type IInternalDebugUIConstants is not
accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1291 Java Problem
Discouraged access: The field
IMG_LCL_COPY_VIEW_TO_CLIPBOARD from the type IInternalDebugUIConstants is not
accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1293 Java Problem
Discouraged access: The method
createControl(Composite) from the type GoToAddressComposite is not accessible
due to restriction on required project org.eclipse.debug.ui Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 192 Java Problem
Discouraged access: The method getButton(int) from
the type GoToAddressComposite is not accessible due to restriction on required
project org.eclipse.debug.ui Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 193 Java Problem
Discouraged access: The method getButton(int) from
the type GoToAddressComposite is not accessible due to restriction on required
project org.eclipse.debug.ui Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 203 Java Problem
Discouraged access: The method getDefault() from the
type DebugUIPlugin is not accessible due to restriction on required project
org.eclipse.debug.ui TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 149 Java Problem
Discouraged access: The method getDefault() from the
type MemoryRenderingManager is not accessible due to restriction on required
project org.eclipse.debug.ui MemoryBrowser.java
/org.eclipse.cdt.debug.ui.memory.memorybrowser/src/org/eclipse/cdt/debug/ui/memory/memorybrowser
line 578 Java Problem
Discouraged access: The method getExpressionWidget()
from the type GoToAddressComposite is not accessible due to restriction on
required project org.eclipse.debug.ui Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 213 Java Problem
Discouraged access: The method getExpressionWidget()
from the type GoToAddressComposite is not accessible due to restriction on
required project org.eclipse.debug.ui Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 218 Java Problem
Discouraged access: The method getExpressionWidget()
from the type GoToAddressComposite is not accessible due to restriction on
required project org.eclipse.debug.ui Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1147 Java Problem
Discouraged access: The method getExpressionWidget()
from the type GoToAddressComposite is not accessible due to restriction on
required project org.eclipse.debug.ui Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1150 Java Problem
Discouraged access: The method
getGoToAddress(BigInteger, BigInteger) from the type GoToAddressComposite is
not accessible due to restriction on required project org.eclipse.debug.ui
Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 491 Java Problem
Discouraged access: The method
getImageDescriptor(String) from the type DebugPluginImages is not accessible
due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1290 Java Problem
Discouraged access: The method
getImageDescriptor(String) from the type DebugPluginImages is not accessible
due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1292 Java Problem
Discouraged access: The method
getImageDescriptor(String) from the type DebugPluginImages is not accessible
due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1294 Java Problem
Discouraged access: The method openError(String,
String, Exception) from the type MemoryViewUtil is not accessible due to
restriction on required project org.eclipse.debug.ui Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1119 Java Problem
Discouraged access: The type DebugPluginImages is
not accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 28 Java Problem
Discouraged access: The type DebugPluginImages is not
accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1290 Java Problem
Discouraged access: The type DebugPluginImages is
not accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1292 Java Problem
Discouraged access: The type DebugPluginImages is
not accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1294 Java Problem
Discouraged access: The type DebugUIMessages is not
accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 29 Java Problem
Discouraged access: The type DebugUIMessages is not
accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1288 Java Problem
Discouraged access: The type DebugUIMessages is not
accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1289 Java Problem
Discouraged access: The type DebugUIPlugin is not
accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 30 Java Problem
Discouraged access: The type DebugUIPlugin is not
accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 149 Java Problem
Discouraged access: The type GoToAddressComposite is
not accessible due to restriction on required project org.eclipse.debug.ui
Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 34 Java Problem
Discouraged access: The type GoToAddressComposite is
not accessible due to restriction on required project org.eclipse.debug.ui
Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 74 Java Problem
Discouraged access: The type GoToAddressComposite is
not accessible due to restriction on required project org.eclipse.debug.ui
Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 191 Java Problem
Discouraged access: The type
IInternalDebugUIConstants is not accessible due to restriction on required
project org.eclipse.debug.ui Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 32 Java Problem
Discouraged access: The type IInternalDebugUIConstants
is not accessible due to restriction on required project org.eclipse.debug.ui
Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 169 Java Problem
Discouraged access: The type
IInternalDebugUIConstants is not accessible due to restriction on required
project org.eclipse.debug.ui TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 31 Java Problem
Discouraged access: The type IInternalDebugUIConstants
is not accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 107 Java Problem
Discouraged access: The type
IInternalDebugUIConstants is not accessible due to restriction on required
project org.eclipse.debug.ui TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 111 Java Problem
Discouraged access: The type
IInternalDebugUIConstants is not accessible due to restriction on required
project org.eclipse.debug.ui TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1291 Java Problem
Discouraged access: The type
IInternalDebugUIConstants is not accessible due to restriction on required
project org.eclipse.debug.ui TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1293 Java Problem
Discouraged access: The type
IInternalDebugUIConstants is not accessible due to restriction on required
project org.eclipse.debug.ui TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1295 Java Problem
Discouraged access: The type IMemoryBlockConnection
is not accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 32 Java Problem
Discouraged access: The type IMemoryBlockConnection is
not accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 93 Java Problem
Discouraged access: The type IMemoryBlockConnection is
not accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1229 Java Problem
Discouraged access: The type IMemoryBlockConnection
is not accessible due to restriction on required project org.eclipse.debug.ui
TraditionalRendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1233 Java Problem
Discouraged access: The type MemoryRenderingManager
is not accessible due to restriction on required project org.eclipse.debug.ui
MemoryBrowser.java
/org.eclipse.cdt.debug.ui.memory.memorybrowser/src/org/eclipse/cdt/debug/ui/memory/memorybrowser
line 38 Java Problem
Discouraged access: The type MemoryRenderingManager is
not accessible due to restriction on required project org.eclipse.debug.ui
MemoryBrowser.java
/org.eclipse.cdt.debug.ui.memory.memorybrowser/src/org/eclipse/cdt/debug/ui/memory/memorybrowser
line 578 Java Problem
Discouraged access: The type MemoryViewUtil is not
accessible due to restriction on required project org.eclipse.debug.ui
Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 33 Java Problem
Discouraged access: The type MemoryViewUtil is not
accessible due to restriction on required project org.eclipse.debug.ui
Rendering.java
/org.eclipse.cdt.debug.ui.memory.traditional/src/org/eclipse/cdt/debug/ui/memory/traditional
line 1119 Java Problem
From: John Cortell [
mailto:rat042@xxxxxxxxxxxxx]
Sent: Monday, May 10, 2010 3:46
PM
To: CDT General developers list.; CDT General developers
list.
Cc: Rohrbach, Randy
Subject: Re: [cdt-dev] building
the Memory Browser and Traditional Renderer
Yes. I sent various
emails on the subject. It's my belief that our plugins should generate zero
warnings, and the memory projects have been set up to try to ensure that (now
that i removed all warnings). Whatever warnings (now errors) you are seeing
should be fixed, not ignored. One such issue was reported this morning
and fixed, and it was due to a subtle difference between Canvas on linux and
Windows that I was not seeing. I'll be happy to investigate and fix any other
issue you are seeing.
John
At 02:40 PM 5/10/2010, Rohrbach,
Randy wrote:
Content-Class:
urn:content-classes:message
Content-Type:
multipart/alternative;
boundary="----_=_NextPart_001_01CAF078.A75F9926"
Folks
I just updated my
Open Source Reference CDT developmemnt space to all
M7.
I needed to reset the
build options errors/warnings for the MemoryBrowser and
TraditionalRenderer to the defaults in order to get them to build. I have
not made
any changes to these components. There were certain
specifications which were
forcing errors where they used to
just be warnings.
I have seen
some emails ( but not followed to closely ) concerning errors
and
warnings changes.
Has anything been changed for these
components.
Thanks for the
info.
Randy
_______________________________________________
cdt-dev
mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev
mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
