Community
Participate
Working Groups
We would like m2e to be added to the Java Developer Package. At this point m2e is still tagged as "incubator" but by the time of the release, the project should not longer be in that state.
Sounds like an addition that would be useful for a large portion of users. To help us better understand the impact could you provide an estimate for the following? * How much would m2e increase the download size of the Java package? * Does m2e ship with a Maven runtime or does that require a separate download, i.e. does m2e require any manual setup? * How many UI contributions does m2e add to the Java perspective? * What is the runtime impact of m2e if it's not used (i.e. no project is configured for a Maven build, all m2e views are closed)?
> * How much would m2e increase the download size of the Java package? It is an additional 9M. The WTP and EMF deps are already included in the package. > * Does m2e ship with a Maven runtime or does that require a separate download, > i.e. does m2e require any manual setup? It ships with a maven runtime. We will have a mechanism to allow ppl to update the runtime. > * How many UI contributions does m2e add to the Java perspective? We only add elements to the context menu of maven enabled project. At this point we don't open any additional view or anything like that. > * What is the runtime impact of m2e if it's not used (i.e. no project is > configured for a Maven build, all m2e views are closed)? No impact expected / known.
Thanks. I don't see any technical reasons against including m2e. I think an additional 9 MB is reasonable considering how wide spread Maven is. I would like to allow sufficient time for testing and community feedback though. What is the earliest milestone m2e could be included in a package build?
(In reply to comment #3) > What is the earliest milestone m2e could be included in a package build? What about the next one? If m2e is available from the Indigo milestone repository it should be very easy. Which feature group should be added?
Back to this one... because there still is a (small) chance to get it in with M4: - How is the status? Should m2e be included in the Java package? - If yes, which feature groups should be included?
Crap, I missed your note from December :) The feature to add is org.eclipse.m2e.feature and our contrib for M5 is already done.
I went ahead and added the feature to the Java package config. It should be available with one of the next builds this week if there are no unexpected problems (typos and such things ;-).
It's there... you may want to look into the last build of the Java package: http://build.eclipse.org/technology/epp/epp_build/indigo/download/20110203-0922/
Looks good to me ! Should I keep the bug open or will new builds automatically pick new versions of the feature from the aggregated repo?
forgot to say, Thx!
AFAIK EPP builds will always use the latest version from the Indigo (or project) repository. Are we one here?
(In reply to comment #11) > AFAIK EPP builds will always use the latest version from the Indigo (or > project) repository. Are we one here? True, it picks always what it can get and what it can install from the Indigo (staging) repository. But it is always a good idea to keep an eye open because there are rare cases where the latest version has some dependencies that cannot be resolved and as a fallback EPP (or p2) takes another version from the release train repository.
m2e seems to be working (at least I found some log files ;-) and included in the Java package. At some point in the future (past Indigo) I would like to think about adding it to other packages (e.g. the RCP/RAP package). Closing this bug as FIXED.
