[m2e-dev] juno work heads up

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

Just to give a heads up.

Shortly after Juno M2 is declared, I am going to switch m2e master
branch to 1.1.0.qualifier version as I plan to introduce some new APIs
needed to support [1] and [2]. As one implication of this change, most
of m2e extensions available from m2e discovery catalog will not install
on m2e juno m3 because they use [1.0,1.1) m2e dependency version range.
I am not sure what to do about this yet. One possibility is to generate
separate catalogs for 1.0 and 1.1 compatible extensions, but if somebody
can suggest more elegant solution I am interested to hear about it.

I also plan to rework packaging of m2e embedded maven runtime and other
"wrapper" bundles. Instead of tycho generate-bundle goal, which has been
removed from tycho 0.13 already, the project will use
maven-bundle-plugin with <Embed-Dependency>. I also made required
changed to m2e-tycho and worked with pde, maven-bundle-plugin, and bnd
developers to make <Embed-Dependency> work inside eclipse workspace. The
end result, all embedded dependencies will be dynamically resolved from
repositories, so switching to new maven version, for example, will be as
easy as changing pom.xml file. Workspace dependency resolution works
too, so it will be possible to make changes to maven and debug the
results in m2e without any intermediate steps.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=353266
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=349586

--
Regards,
Igor