Before recommending every package uses a qualifier I have the following
concerns:
1) In Eclipse we have loads of packages. We better make sure all identical
qualifier Strings are shared (interned etc.) for performance reasons.
Today when loading from a cached state we share identical Version
I would be extremely cautious about using qualifier on package versions. I
must say that I have never seen it done.
It seems an over specification. I think that having build tools to advise
you to increment the micro is more than sufficient.
--
BJ Hargrave
Senior Technical Staff Member, IBM
API Tooling also has
items in plan that deal with package versioning, but that will be post
M2
FYI - plans for package version support in API tooling have been reduced.
Currently, there is nothing on the draft plan due to resources available
to do the work, and the fact that SDK plug-in
Here are some obvious questions:
* How are @since tags formatted to indicate that the version number
corresponds to packages vs. bundles?
If there is a package version then the @since should always reference
the package version exported in my opinion.
* How are initial package versions
Ricardo,
I have this working with GWT 1.5 and Eclipse 3.4, so we know it's
possible :-).
Have you tried adding javax.servlet to the required plug-ins for GWT? I
have a GWT bundle, and I noticed that it depends on javax.servlet. If I
remove this dependency I get the class cast exception.
I
Darin Wright
Eclipse Debug Lead,
Rational Team,
IBM Canada
(204)938-8051
[EMAIL PROTECTED] wrote on 09/02/2008 01:59:00 PM:
Here are some obvious questions:
* How are @since tags formatted to indicate that the version number
corresponds to packages vs. bundles?
If there is a
Right, but since package versions will now evolve independently of
bundle
versions, should the package name also appear in the @since tag - like
@since org.eclipse.jdt.debug.model 3.4. Else, when just looking at the
Javadoc, consumers of an API will not know if they need a required
Right, but since package versions will now evolve independently of
bundle
versions, should the package name also appear in the @since tag - like
@since org.eclipse.jdt.debug.model 3.4. Else, when just looking at
the
Javadoc, consumers of an API will not know if they need a required
