Hi Jason,
Jason van Zyl wrote:
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).
So I guess I now need to ask: what is the Maven Eclipse Extension?
Didn't find via google search. Does it use/depend upon the Maven 2
embedder or does is use some other part of Maven? And is there a
development/release plan associated with the Maven Eclipse Extension?
I think it's a terrific/necessary idea to reuse the classpath (and other
meta info/dependency info) within Eclipse itself, as trying
to/rewriting/keeping in synch all of that code (to parse manifest.mf,
.classpath, .project, plugin.xml, feature.xml, site.xml) would really be
a waste since Equinox and PDE does this already (as it obviously has to).
Thanksinadvance,
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
