> According to the naming guidelines, this should be the same as > the third segment of the package and bundle names.
It sounds to me like the naming guideline should be updated as this doesn’t properly account for multiple nesting of projects. While in cases like technology project, the parent project can be skipped in the namespaces, in cases like WTP, the project hierarchy should be reflected in the namespace. Since WTP was restructured post initial namespace assignment, there is no singular existing namespace for WTP Java EE Tools project. The “jst.jee” namespace has been the recent trend for new functionality, hence my choice to use it as the base. - Konstantin From: [email protected] [mailto:[email protected]] On Behalf Of Wayne Sent: Monday, June 20, 2011 4:14 PM To: General discussion of project-wide or architectural issues. Subject: Re: [wtp-dev] Plugin and package namespace for the Java EE Module Configuration Editors Strictly speaking, asked for the namespace so that I could use it as the project short name in our db. According to the naming guidelines, this should be the same as the third segment of the package and bundle names. In the future, I do intend to start asking for package names in proposals. HTH, Wayne Konstantin Komissarchik <[email protected]> wrote: EMO is asking me to include the namespace for this work in the proposal. Obviously, this needs to work with the rest of the Java EE Tools project. I have come up with the following proposal: org.eclipse.jst.jee.config There would be sub-packages under that for different module types and ui vs non-ui code. Thoughts? - Konstantin
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
