In my maven project in eclipse some of the imported interfaces has a diagonal cross line on its icon.
Why there is that diagonal cross line on the interface icon?
Do you mean like this?
This is because the interface is marked as deprecated (with the #Deprecated annotation).
This is a sign to not use the interface anymore, because it might be deleted in newer versions of the lib.
Related
is it possible to change icons for project view in NetBeans? Class, enum and interfaces have all crazy similar icons so its purpose to distinguish its file function in project is gone.
Update: https://pasteboard.co/HwQw5Zn.png <-
This issue was previously raised with NetBeans 7 as a bug, and the outcome of that is the icons you see now! See NetBeans Bug 225049 - Different icons for classes and interfaces (and possibly abstract classes, enums and annotations) for the details.
The class and enum icons in the Projects panel certainly still look very similar to me, though individual eyesight, monitor quality and screen resolution are also relevant.
Unfortunately there is no way for the user to customize these icons; they are internal to NetBeans. It's also unfortunate that there is no way to adjust the size of the icons. Even if you increase the size of the font used by NetBeans (by setting --font_size in netbeans.conf) the size of the icons is not increased.
The situation is doubly frustrating because the three icons used to represent a class, an enum and an interface in the Navigator panel are much more distinguishable than the rectangular "paper" icons for the corresponding files in the Projects panel:
The situation is unchanged in the recent release of NetBeans 9. It is very unlikely that this will ever be addressed in NetBeans 8.2, so I can only suggest that you create a new bug for NetBeans 9.
Which extension point can I use in order to extend the bottom part of the eclipse interface?
I am referring to the part as seen above:
I am interested in the File Search... section.
Is there a way i can display fully qualified class names for the debugger's callstack?
E.g. rather than this:
I would like to have the packages of the classes included - like where the green boxes remain here:
(NOTE: Actually i dont care where they are displayed as long as there is a easy way to determine the package of a class in the callstack)
Motivation:
I am currently working on legacy systems where there is multiple layers of frameworks (both self-made as well as old stuff like Struts 1.1.), service components etc. etc. and i try to figure out the first point our code is included in some way). Since there are now about 100 Projects in my Eclipse -all with their Maven dependencies - things get complicated by just "Link with Editor" and see where the according class is placed in.
What i tried:
Aprox. 20min Webresearch (incl. reading the SO questions/ answers recommended when i created this question) without any remarkable results.
Using my entire design skills combinated with my 15+ years of MS Paint experience i drew the above images (Feel free to add those stunners to your art collection).
Does this help? In the upper right-hand corner of the Debug (callstack) view, click the menu button (the upside down white triangle), then Java, then see the 'Show Qualified Names' option.
Greetings fellow Stackoverflownians,
I am developing an Eclipse RCP plugin, and have come across different icons in the Dependencies tab of the manifest file:
Anybody got a clue why the last one is different? My supposition is that it's coming from a different source, i.e. the Build Path, instead of the Target Platform.
It's a nebula for me, to be honest.
Any opinions and suggestions are appreciated!
It seems to be that icon on 'some.project.here' icon means the plugin is in your workspace, the other icon means the plugin comes from the target platform.
You can also get a small question mark overlayed on the image which means the plugin is optional. There is also a small arrow overlay which means the plugin dependency is marked as re-exported.
There is also an 01 overlay which I think means this a project imported using 'import plugins and fragments' with 'binary project' selected.
Maybe it has something to do with the fact that the plugin you are adding is in your package explorer.
Yep you're right. The arrow means definitly that eclipse will resolve the dependency from the TargetPlatform. And the other one with the dot indicates, that it will resolve it from your local workspace.
I've built my own IClasspathContainer to link in a 3rd party JAR. On occasions no JAR can be found and getClasspathEntries return an array of zero IClasspathEntry objects.
The effect this has on the project tree is unexpected - the library/classpath-container vanishes from the project display altogether.
Ideally the library icon would remain in the project tree, leaving me something to decorate to indicate the error. More ideal still, I could decorate the root project icon to indicate a build error.
Can anyone advise how I might achieve this - if achievable at all?
M.