Hi Jason,
Jason van Zyl wrote:
On 11 Dec 06, at 8:22 PM 11 Dec 06, Scott Lewis wrote:
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?
Boy, you have a short memory :-)
I suppose I do. :). But in my own defense: !"Maven Eclipse
Extension".equals("m2eclipse").
http://archive.m2eclipse.codehaus.org/dev/454134FB.4080208%40composent.com
Unless you're a different Scott Lewis.
No, that's me.
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?
Whole bunch of hits there but the important ones are:
http://jira.codehaus.org/browse/MNGECLIPSE
and the archives for anyone not familiar with the project:
http://archive.m2eclipse.codehaus.org/
So m2eclipse *does* depend upon the Maven embedder currently...and at
the moment there is no way to use the meta info in manifest.mf,
plugin.xml, (and read/changed in memory in the PDE) to 'build' a pom
representationand have the Maven embedder operate on it/with it.
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).
It would be nice unfortunately stuff needs to be unified on the
Eclipse side first so Jeff said he would help facilitate that with Tom
on the resolver side and Wassim(sp?) on the container side.
What needs to be unified on the Eclipse side first? The PDE currently
does all this and the Jeff is the lead for the Equinox team (which also
includes Pascal Rapicault, one of the PDE developers along with others
connected with the Equinox team). As far as I know doesn't have any
outstanding work items to do anything specific to unifying things for
Maven.
I'm meeting/seeing Jeff on Wednesday am at foundation BOD meeting, so if
there is some required change to the PDE or Equinox then I would be
happy to speak with him about it directly. But I would need to
understand what exactly was required of them and why, as I have spoken
with Jeff about Maven integration before.
Thanks,
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
