Breaking changes to the archetype API -> m2e 2.0?
by Fred Bricon
Hi,
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).
I checked it fixes the following issues :
- https://bugs.eclipse.org/459453,
- https://bugs.eclipse.org/424010,
- https://bugs.eclipse.org/394918,
- https://bugs.eclipse.org/374660,
- https://bugs.eclipse.org/405945 (on OSX at least),
- https://bugs.eclipse.org/415114,
- https://bugs.eclipse.org/429287
Bugs https://bugs.eclipse.org/446657, https://bugs.eclipse.org/348893 may
or not be fixed (I can't test proxies)
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.
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.
Given that I'm also in charge of the JBoss Tools integration, I'm fine with
the impact :-)
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 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?
Fred
--
"Have you tried turning it off and on again" - The IT Crowd
11 years, 1 month
ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.2.x -> tag jbosstools-4.2.3.CR1 ]
by Nick Boldt
Component leads, please tag your repositories!
(Note: if you changed nothing in this milestone, you don't have to tag.
Looking at you, Portlet & Freemarker.)
$ git fetch jbosstools jbosstools-4.2.x #assuming remote is called
jbosstools, also often called origin
$ git tag jbosstools-4.2.3.CR1 FETCH_HEAD
$ git push jbosstools jbosstools-4.2.3.CR1
Then, once tagged, *IF YOU CONTRIBUTED FIXES IN Beta1 or CR1 ONLY*
please bump your root pom to use the latest parent pom,
4.2.3.Final-SNAPSHOT.
I will send out the usual Task JIRA nags, too.
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
11 years, 1 month
Bug in Forge/JBDS 8.1.0.CR1, do we really need a respin?
by Alexey Kazakov
Hi,
We have an issue in the latest Forge 2.15.1.Final (upgraded in JBDS
8.1.0.CR1) - https://issues.jboss.org/browse/JBIDE-19468
It prevents creating a forge addon. The workaround described in the JIRA.
The issue itself doesn't look like a blocker for JBDS 8.1 to me.
However, George Gastaldi said that they are going to release a fixed
Forge 2.15.2 today or tomorrow and *IF* we can do a respin for the forge
component (with upgraded forge) *with no big cost* maybe it's worth doing.
WDYT?
11 years, 1 month
