| FWIW,
we have a dependency to m2e runtime. With m2e’s move to 1.5 and switching from Sonatype Aether to Eclipse Aether Incubation we have a similar issue.
We can fall back to the 1.4 maven runtime, though. A release of Eclipse Aether (this component contains 98% of what we need) would help - but I’ve no insight into Eclipse Aether release plans [1].
Hello,
I just pushed updated version of m2e 1.5 plan.xml to our git
repository [1]. I will let technology pmc and other eclipse powers
decide if this is good enough for m2e to stay in simultaneous release.
Also, in line with our "use latest released maven" recurring theme, we
updated m2e to include maven 3.1.1 earlier this year and there is a
50/50 chance will update to maven 3.1.2, provided it is released before
luna ip deadline. Problem is, maven 3.1.x includes Eclipse Aether and
Eclipse Sisu binaries, both currently under incubation as eclipse
technology project.
My questions are
Can m2e get an exception to ship incubating components in a mature
project on the grounds that m2e includes released maven version, which
just happens to include eclipse incubating project binaries?
If m2e has to go back to incubation, will "java" and "java ee" epp
package maintainers be willing to keep m2e in?
[1] http://git.eclipse.org/c/www.eclipse.org/m2e.git/commit/?id=6c18b3cf58143f5f462f2f3b601ef2996887ef07
--
Regards,
Igor
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
