I had a small discussion with Tamas on IRC yesterday about this, and I
did come to realize that the proper way to do this is to do a regular
release of maven-archiver 2.4.2, then make a branch in svn for
maven-jar-plugin 2.3.2. On the branch, update to maven-archiver 2.4.2
and then release
On Fri, Aug 19, 2011 at 4:01 PM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
I had a small discussion with Tamas on IRC yesterday about this, and I did
come to realize that the proper way to do this is to do a regular release of
maven-archiver 2.4.2, then make a branch in svn for
Den 19.08.2011 09:04, skrev Barrie Treloar:
On Fri, Aug 19, 2011 at 4:01 PM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
I had a small discussion with Tamas on IRC yesterday about this, and I did
come to realize that the proper way to do this is to do a regular release of
+1 for the upgrade in principal. It's not the best solution, but the best
solution quickly available.
Maven should nontheless introduce an own simplified SPI for that stuff and use
it in maven-core. All aether stuff should really only be handled in the
maven-aether-provider and we should
Hi folks!
I know aether @eclipse should be starting in the next weeks. But it will
certainly take a few more weeks to get all the packages renamed (most
probably), etc.
Should we create a 3.0.4 with the old aether package names now and start with
the upgrade later?
+1 from me.
LieGrue,
+1 from me too.
Kristian
Den 19.08.2011 11:34, skrev Mark Struberg:
Hi folks!
I know aether @eclipse should be starting in the next weeks. But it will
certainly take a few more weeks to get all the packages renamed (most
probably), etc.
Should we create a 3.0.4 with the old aether package
Den 19.08.2011 11:34, skrev Mark Struberg:
Hi folks!
I know aether @eclipse should be starting in the next weeks. But it will
certainly take a few more weeks to get all the packages renamed (most
probably), etc.
Should we create a 3.0.4 with the old aether package names now and start with
Mark,
I think you're jumping the gun a bit. The vote that Arnaud proposed is not
finished yet. Many PMC members have not voted yet and at the very least to
short-circuit the vote we need to reach a majority amongst the PMC. Once that
happens then I think we can start discussing a 3.0.4
I think the outcome of the other vote doesn't change much.
The following scenarios are possible:
a.) The vote fails and maven stays at aether 1.11. In this case we still should
ship a 3.0.4 to fix a few bugs on our side.
b.) The vote passes and aether @eclipse must change package names + GAV
I misread you, sloppy of me. EPL aether waits; we could do 3.0.4 for
other non-aether stuff.
Kristian
Den 19.08.2011 13:32, skrev Mark Struberg:
I think the outcome of the other vote doesn't change much.
The following scenarios are possible:
a.) The vote fails and maven stays at aether
+1.
It seems a sensible plan to me.
First release a 3.0.4 ASAP to show Maven keeps moving.
Then release a 3.0.5 when Aether and Sisu will have thoroughly finished
their landings at eclipse.
Cheers
Le 19 août 2011 13:32, Mark Struberg strub...@yahoo.de a écrit :
I think the outcome of the other
I think we should wait for the vote to finish as it appears the vote will pass
and then a release can be made that users actually want. That fixes are are
most requested fall into the category of requiring the newer versions of Aether
and Sisu.
I'm certain users would be more interested in
There is more beyond that. Remember that we also upgraded to wagon-1.0 which
had some _serious_ fixes, etc. + upgrade to the new apache parent and other
stuff which have been no maven-core part directly, but got fixed subsequently.
LieGrue,
strub
--- On Fri, 8/19/11, Jason van Zyl
I'll add my opinion as a Maven user and someone outside of the dev team:
My first hand choice would be a 3.0.4 with Aether and Sisu fixes. My
take on the discussions is that including Aether 1.12 is possible
license vice, but there was some concerns having a dependency on
something not being
As long as we reach consensus about whether we should release. At this point
we've wait this long, if we were going to release 3.0.4 sans Aether 1.12 we
should have done it a month ago. Right now the best thing for users is to make
the best possible release and that includes Aether 1.12 which
I'm thinking like Jason. If we wanted we to release 3.0.4 without Aether we
should have done that 2 or 3 weeks ago (I think Wagon 1.0 was already ready
?).
I'm almost sure that Jason will convince Eclipse to keep the current
identity of these projects (at least for a period of time to let him
http://maven.apache.org/wagon/wagon-providers/wagon-ssh/
Try the breadcumbs. some of them point to 'people.apache...'. I might
have done this, but I need help fixing in any case.
-
To unsubscribe, e-mail:
Arnaud, are you talking about a Maven 3.0.4 release with Eclipse
Aether+Sisu or with Sonatype Aether+Sisu?
/Anders
2011/8/19 Arnaud Héritier aherit...@gmail.com:
I'm thinking like Jason. If we wanted we to release 3.0.4 without Aether we
should have done that 2 or 3 weeks ago (I think Wagon
For what it's worth, working around Maven not having had a release since the
1.12 release of Aether has been an unwelcome hassle. (FYI, I reported one
of the issues Jason mentioned, MNG-5087.)
I don't have much perspective on the intricacies or history of the licensing
and governance issues that
+1
On 2011-08-18 11:23, Arnaud Héritier wrote:
Hi all,
Thus as decided with Mark and Kristian I relaunch a new vote with a better
scope about what we are voting for.
Next releases of SISU and Aether will be released at Eclipse.org under EPL
1.0 license.
Before they were published
+1 binding for the upgrade
I echo Mark's comments about SPI and maven-aether-plugin.
Wayne
2011/8/18 Arnaud Héritier aherit...@gmail.com:
Hi all,
Thus as decided with Mark and Kristian I relaunch a new vote with a better
scope about what we are voting for.
Next releases of SISU and
On 8/19/11 5:32 AM, Mark Struberg wrote:
+1 for the upgrade in principal. It's not the best solution, but the best
solution quickly available.
Maven should nontheless introduce an own simplified SPI for that stuff and use
it in maven-core. All aether stuff should really only be handled in
The Maven team is pleased to announce the release of the parent POMs for Maven
projects: version 21 for Maven parent, version 22 for Maven Plugins parent and
version 17 for Maven Shared Components parent.
http://maven.apache.org/pom/maven/
http://maven.apache.org/pom/maven-plugins/
+1 (binding)
-Stephen
On 19 August 2011 10:32, Mark Struberg strub...@yahoo.de wrote:
+1 for the upgrade in principal. It's not the best solution, but the best
solution quickly available.
Maven should nontheless introduce an own simplified SPI for that stuff and
use it in maven-core. All
On Fri, Aug 19, 2011 at 5:01 PM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
[del]
After some time with git you just start using branches for anything you
feel like, and imposing that kind of constraint now seems strange. So I
bring that back to svn ;)
Off topic.
I use Eclipse to
On Sat, Aug 20, 2011 at 5:03 AM, Wayne Fay wayne...@gmail.com wrote:
+1 binding for the upgrade
I echo Mark's comments about SPI and maven-aether-plugin.
+1 binding
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
26 matches
Mail list logo
