Community
Participate
Working Groups
m2e comes with 2.0-alpha-4 version of archetyper runtime, which does not honour maven http proxy configuration and project creating fails in some environments because of this. The bug is fixed in now released archetyper 2.0, but from my understanding there were major changes in archetyper between alpha-4 and final 2.0, so update most likely be more involved than jar swap. Another complication is getting new archetyper jars cleared through eclipse IP review process. Original m2e bugreport https://issues.sonatype.org/browse/MNGECLIPSE-1910 Archetype bugreport http://jira.codehaus.org/browse/ARCHETYPE-202
In the past concerns had been expressed wrt moving to this new version. Which transport is being used by the archetype system?
I don't know if that error is related, but once in a while (about 50% of the times) I get the following exception when trying to create a maven module/project from a local (!) archetype: Error downloading archetype <groupId>:<artifactId>:<version>. Unfortunately there is no stacktrace available in the log. Without a stacktrace it is hard to say, whether this is a bug from archetyper runtime or not, but presumably this is also fixed with the new version.
closing old/stale bugreports
*** Bug 459453 has been marked as a duplicate of this bug. ***
I have an initial POC that uses archetype 2.3. I checked it fixes bugs #459453, #424010, #394918, #374660, #405945 (on OSX at least), #415114, #429287 Bug #446657, #348893 may or not be fixed (I can't test proxies) The only problem is it will break 3rd party adopters (JBoss Tools at least) depending on the archetype API (package/class names changed between 2.0.0.alpha4 and 2.3) Getting the fix in will require m2e to bump its version to 2.0 (and open a bunch of CQs in ipzilla) I'd really like to get that in for Eclipse Mars, if possible, WDYT?
Gerrit changest https://git.eclipse.org/r/#/c/44277/1 No regression detected while running ITs Now the question is, does it really require upversioning m2e to 2.0?
m2e-dev is the proper place to discuss this, but my tentative opinion, new archetyper does not require m2e 2.0. In other words, we can ship new archetyper with m2e 1.6
So commit http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=9a3c27c321e2ad5766034c88578fe35d1d09556c applied without changing the major version All archetype packages (org.eclipse.m2e.core.archetype, org.apache.maven.archetype.*, org.codehaus.plexus.velocity) have been marked as x-internal:true
Resolving for 1.6.M6
Resolving twice (thanks bugzilla)
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
