I don't expect M2 specific changes on the shared component anymore, so I
think we those projects are ready to be merged back to the trunk.
That is:
- maven-artifact-transfer
- maven-common-artifact-filters
- maven-dependency-tree
Let me do that the following period, including the creation of matching
JIRA issues to trace back all changes
Robert
Op Sun, 07 Jun 2015 17:52:24 +0200 schreef Kristian Rosenvold
<kristian.rosenv...@gmail.com>:
And I appreciate your work a lot. I've got the assembly-plugin migration
in
github and I'll just land that right on trunk once I'm happy with it.
Kristian
2015-06-07 17:35 GMT+02:00 Robert Scholte <rfscho...@apache.org>:
Hi,
I've made those branches to see how much work it is to drop M2 support
and
to not lose my work.
And it is quite a lot. I still haven't covered everything.
I'm actually happy I didn't use the trunk for it, since now it was
possible to do a 2.x release of the maven-shade-plugin.
Now we're on it, for surefire the ArtifactResolver[1] needs to be
replaced
for 3.0.
I still see activity for surefire-2.x, so I'll wait to work on those
changes until one has decided to go for 3.0
thanks,
Robert
http://maven.apache.org/components/ref/3.0/maven-compat/xref/org/apache/maven/artifact/resolver/ArtifactResolver.html#49
Op Sun, 07 Jun 2015 14:45:24 +0200 schreef Kristian Rosenvold <
kristian.rosenv...@gmail.com>:
Do we really need to keep the 3.0 versions in branches ? Can't we just
make
a branch if we need to fix something in the 2.x range ?
Kristian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
