|Re: [wtp-dev] Plugin and package namespace for the Java EE Module Configuration Editors|
Not quite sure what you are saying here, but my comment was purely a response to your statement in previous e-mail that project short name must be the third segment of the bundle/package namespace. I was merely pointing out that it doesn’t work in this case. Reading the actual guidelines, it doesn’t look like the “third segment” is stated anywhere as such. More of a general “short name should start at third segment” statement, which is consistent to what was proposed.
Bottom line… Is the proposed namespace and the short name of “jst.jee.config” ok with EMO? Note that we still need to hear from Chuck Bridgham for Java EE Tools Project ok.
Take a harder look at the guidelines.
> 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.
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.
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:
There would be sub-packages under that for different module types and ui vs non-ui code.
Back to the top