sverhagen wrote:
Wouldn't it be less nesting if you open resources from nested modules
not from the parent project, but from within module projects?
Personally I kind of don't like word "useless". If it is useless, why
did you created so many folders to begin with? :-)
I didn't (I'm just interested in the root of my project1). So my whole point
is to get rid of them ;-)
Basically if you will use a little bit of self discipline and stop
opening module resources and java files from the root of your project it
is all going to be good, right? :)
- "Link with Editor" not working in Package Explorer
This one I can't reproduce. Technically, same resource shown in
different subtrees actually have different path in workbench and from
what I see, Package Explorer in Eclipse 3.4 works just fine:
/test-foo/test-module/src/main/resources/test.properties
/test-module/src/main/resources/test.properties
Well, strangely enough, I only have this problem for .java files (so far).
It'll show the Java file with a different icons, AFAIK to indicate that it
does not know this file as part of the workspace.
http://www.nabble.com/file/p18698772/amount-java.jpg
All it means that there is a .java file that didn't come from source
folders. Seem like you have opened it from your parent1 folder and that
is quite expected not to work.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
