Community
Participate
Working Groups
In a recent survey (ATC), I don't think anyone was in favor of package nesting (like in VA-Java). I do think however that resource nesting makes sense. I don't believe it was brought up. For example, I have the package "p1". And, I have the resource "p1/foo.properties" And, I have the resource folder "p1/icons/" The resource "foo.properties" currently shows up under the package in the Packages View. I would like to see the "icons" folder under the package as well.
this would require additional support from the JavaModel that is unlikely to happen for 2.0. Moving to JDT CORE
Why would you need anything from the JavaModel for this one ? Isn't this only a consequence of the UI hiding empty packages, no ?
This is a consequence of the Java model "flattening" all the children under a package fragment root, e.g. junit swingui icons becomes junit.swingui junit.swingui.icons
Agreed, but couldn't the rendering of empty packages be resource children of enclosing packages ? From the model standpoint, it makes good sense that any folder under a package fragment root be a package...
currently the packages view structure is isomorphic with the JavaModel (well minus dummy package fragment roots). We will not change this for 2.0
Chaning state from assigned later to resolved later. Assigned later got introduced by the last bug conversion and is not a supported Eclipse bug state.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.