API tooling will provide for bundle version number validation.
Darin Wright
Thomas Watson [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
01/11/2008 04:24 PM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
Equinox development mailing list equinox-dev@eclipse.org
cc
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
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
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
/java/swing/plaf/windows/*. You'll likely need to use the
org.osgi.framework.system.packages.extra system property to make the
package visible at runtime to.
Darin Wright
From:
Thomas Watson tjwat...@us.ibm.com
To:
Equinox development mailing list equinox-dev@eclipse.org
Date:
06/30/2009 11:03
