<div dir="ltr"><div>Hi,</div><div><br></div><div>I have an initial POC that uses maven-archetype-plugin 2.3, instead of the 2.0.alpha4 version (which was released in the 17th century, give or take).</div><div><br></div><div>I checked it fixes the following issues :</div><div>- <a href="https://bugs.eclipse.org/459453" style="border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:orange" target="_blank">https://bugs.eclipse.org/459453</a>, </div><div>- <a href="https://bugs.eclipse.org/424010" target="_blank">https://bugs.eclipse.org/424010</a>,</div><div>- <a href="https://bugs.eclipse.org/394918" target="_blank">https://bugs.eclipse.org/394918</a>, </div><div>- <a href="https://bugs.eclipse.org/374660" style="border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:orange">https://bugs.eclipse.org/374660</a>, </div><div>- <a href="https://bugs.eclipse.org/405945" style="border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:orange">https://bugs.eclipse.org/405945</a> (on OSX at least), </div><div>- <a href="https://bugs.eclipse.org/415114" style="border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:orange">https://bugs.eclipse.org/415114</a>, </div><div>- <a href="https://bugs.eclipse.org/429287" style="border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:orange">https://bugs.eclipse.org/429287</a></div><div><br></div><div>Bugs <a href="https://bugs.eclipse.org/446657" style="border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:orange">https://bugs.eclipse.org/446657</a>, <a href="https://bugs.eclipse.org/348893" style="border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:orange">https://bugs.eclipse.org/348893</a> may or not be fixed (I can't test proxies)</div><div><br></div><div>Most of these issues were automatically closed already after 1 year of inactivity. Doesn't mean the bugs are not there. My level of annoyance just reached a point where I'd like to take action now.</div><div><br></div><div>The only problem with the archetype update is it will break 3rd party adopters (JBoss Tools at least) depending on the archetype API (package/class names changed between 2.0.alpha4 and 2.3). I don't plan on introducing a compatibility layer, not worth the hassle IMHO.</div><div>Given that I'm also in charge of the JBoss Tools integration, I'm fine with the impact :-)</div><div><br></div><div>Getting the fix in will require m2e to bump its version to 2.0 (and open a bunch of CQs in ipzilla)</div><div><br></div><div>I'd really like to get that change in for Eclipse Mars, if possible. Is it too late from a release plan standpoint (i.e. 1.6 -> 2.0)? PMC, fellow m2e committers wdyt?</div><div><br></div><div>Fred</div><div><br></div>-- <br><div>"Have you tried turning it off and on again" - The IT Crowd</div>
</div>