On 11 Dec 06, at 9:10 PM 11 Dec 06, Scott Lewis wrote:
Hi Jason,
Jason van Zyl wrote:
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.
No, waiting for the state resolver to drop out and then I can make a
project builder that attempts to make use of it for doing OSGi/
Eclipse Plugin work. So when that happens we can give that side of it
a whirl. There's all sorts of other interesting things to worry about
in the meantime like integrating Archetypes (basically taking the
work Milos has done for Netbeans), Maven SCM, project bootstrapping
(or workspace materialization I think Buckminster calls it) all of
which will be of interest to Maven users. Eugene is not happy with
the extension in its current state but when he is I would like to
bring it here along with the IDEA integration, and I'm working with
Milos/Netbeans to bring the Netbeans integration here as well.
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?
Jeff said that versions of the State resolver are used in various
incarnations in several places and the within Eclipse land he would
like to unify this
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.
It's not for Maven, it's something that would benefit Eclipse and
Maven would be a by product beneficiary. I asked "where's the code",
to which he replied "well, in several places". So in order for us to
consume it there would have to be something concrete we could use.
What Eugene has now is workable for non-OSGi developers but won't cut
it otherwise.
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.
Unify your State resolver code so we can use it. That's it really.
Jason.
Thanks,
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]
