On 11 Dec 06, at 7:13 PM 11 Dec 06, Scott Lewis wrote:
Hi Tom,
A quick comment: with Eclipse, version dependency requirements can
be specified at the level of individual bundles/plugins and at the
level of features (sets of plugins).
This is described in that document under these subsections
How to specify plug-in requirements: http://wiki.eclipse.org/
index.php/Version_Numbering#How_to_specify_plug-in_requirements
Versioning features: http://wiki.eclipse.org/index.php/
Version_Numbering#Versioning_features
I'm sure this conclusion is obvious to all, but for Maven to 'know'
about and resolve these inter-plugin and inter-feature version
dependencies, it's got to understand the version requirements info
located in manifest.mf (at plugin level) and feature.xml (at
feature level).
We would purely delegate to the State resolver in Equinox. I have
talked with Jeff McAffer about trying to get this resolver cleaned up
and packaged up separately. It's used by in various bastardized
versions in a few places and I talked to Tom Watts briefly at
ApacheCon. Once this is done we could reuse it. Jeff took a first
stab at decoupling quite some time ago. We are attempting to use this
so we can completely reuse the classpath container code in Eclipse
itself inside the Maven Eclipse Extension (which should hopefully be
landing here at some point in the near future).
Jason.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
