This vote has passed with the following votes:
+1 (binding): John, Benjamin, Brett, Brian, Lukas
+1 (non-binding): Nicolas
I'll promote the artifacts and deploy the site changes.
Thanks,
-john
John Casey wrote:
Hi,
I've resolved the issue with plexus-interpolation, reverified the ITs,
and
+1, the issues I had with pre-emptive auth in the last one are fixed.
On Sun, Jun 28, 2009 at 1:01 PM, Benjamin
Bentmann wrote:
> John Casey wrote:
>
>> We've solved 28 issues for this release:
>>
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15103
>
On 30/06/2009, at 5:02 AM, Benjamin Bentmann wrote:
John Casey wrote:
So, would you say it'd be better to reopen 3057 and assign it to
3.x, or open a new issue that references 3057 and 4167, and assign
that to 3.x?
That's actually the question that I couldn't answer for myself and
the
Okay, that's done. MNG-4223 is the new issue if you're interested.
Benjamin Bentmann wrote:
John Casey wrote:
So, would you say it'd be better to reopen 3057 and assign it to 3.x,
or open a new issue that references 3057 and 4167, and assign that to
3.x?
That's actually the question that I
John Casey wrote:
So, would you say it'd be better to reopen 3057 and
assign it to 3.x, or open a new issue that references 3057 and 4167, and
assign that to 3.x?
That's actually the question that I couldn't answer for myself and the
only other opinion so far was an "Agreed" by Brett on an "
That's a fair point. So, would you say it'd be better to reopen 3057 and
assign it to 3.x, or open a new issue that references 3057 and 4167, and
assign that to 3.x?
I lost track of the original reason 4167 was opened, which has indeed
been resolved. Apologies for not paying attention to the p
John Casey wrote:
I've backed out all version-expression transformation, including the
code that was added in 2.1.0-*.
Yup, got that.
So, 4167 isn't fixed to my knowledge.
I basically don't follow your comment on MNG-3538:
> This issue duplicates the reports in MNG-3057 and MNG-4167
To re
I've backed out all version-expression transformation, including the
code that was added in 2.1.0-*. The reason for this is that
version-expression transformation causes critical problems with GPG,
etc. that are blockers for doing releases and such. After exploring this
issue thoroughly to addr
+1Nicolas
2009/6/29 Lukas Theussl
>
> +1
>
> -Lukas
>
> John Casey wrote:
>
>> Hi,
>>
>> I've resolved the issue with plexus-interpolation, reverified the ITs, and
>> restaged the release. The URLs below have been updated. Let's see if we can
>> get through this vote without further interruption
+1
-Lukas
John Casey wrote:
Hi,
I've resolved the issue with plexus-interpolation, reverified the ITs,
and restaged the release. The URLs below have been updated. Let's see if
we can get through this vote without further interruption, I guess.
See also the documentation improvements listi
On Mon, Jun 29, 2009 at 4:28 AM, Paul Benedict wrote:
> Will the release notes contain any general justification for an
> upgrade? For example, can it highlight the major improvements between
> 2.1 and 2.2? or 2.0 and 2.2?
>
+1
Totally agree. It starts to be very difficult for user to follow/u
On 29/06/2009, at 3:01 AM, Benjamin Bentmann wrote:
John Casey wrote:
We've solved 28 issues for this release:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15103
The release history seems a little confusing. For instance, MNG-3538
was listed but
Will the release notes contain any general justification for an
upgrade? For example, can it highlight the major improvements between
2.1 and 2.2? or 2.0 and 2.2?
On Sun, Jun 28, 2009 at 12:01 PM, Benjamin
Bentmann wrote:
> John Casey wrote:
>
>> We've solved 28 issues for this release:
>>
>>
>> h
John Casey wrote:
We've solved 28 issues for this release:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15103
The release history seems a little confusing. For instance, MNG-3538 was
listed but actually duplicates an unresolved issue. I think dups
Hi,
I've resolved the issue with plexus-interpolation, reverified the ITs,
and restaged the release. The URLs below have been updated. Let's see if
we can get through this vote without further interruption, I guess.
See also the documentation improvements listing below for more
information on
Hey, you're doing great work pulling the quality of Maven releases
up... no need to apologise
-Stephen
2009/6/26 John Casey :
> I really can't believe I'm doing this, but I upgraded plexus-utils to get
> rid of a process leak and then re-rolled this staged release...without
> remembering that we
I really can't believe I'm doing this, but I upgraded plexus-utils to
get rid of a process leak and then re-rolled this staged
release...without remembering that we had a similar issue in
plexus-interpolation.
I need to reopen MNG-4219 and upgrade plexus-interpolation to handle
this problem,
I've redeployed the staging repository for this vote:
https://repository.apache.org/content/repositories/maven-staging-013/
The binary distro and source-release artifact are here:
https://repository.apache.org/content/repositories/maven-staging-013/org/apache/maven/apache-maven/2.2.0/
This red
It looks like the mavenVersion property didn't get updated properly for
this staged release. I'll republish with a new repository, and send
along that link. First, I'm dropping the staging repository mentioned
below, to keep people from getting confused.
-john
John Casey wrote:
Hi,
I'm open
Hi,
I'm opening yet another new vote for Maven 2.2.0 after closing:
http://jira.codehaus.org/browse/MNG-4213
See also the documentation improvements listing below for more
information on docs related to this issue.
[NOTE] this release is contingent upon the successful release of Maven
Wagon
Just as a side note, I don't thing the wiki page
http://docs.codehaus.org/display/MAVEN/Maven+2.2.0+Release+Plan is up to
date with current release candidate, is it ?
Nicolas
2009/6/22 John Casey
> I've added this sort of configuration, but I need to document it. I've got
> a proposed next relea
I've added this sort of configuration, but I need to document it. I've
got a proposed next release of wagon staged, and as soon as I get the
documentation for this configuration done, I'll call the vote.
-john
Brett Porter wrote:
On 20/06/2009, at 2:29 AM, Brian Fox wrote:
This is probably
done. I'll finish up the log4j stuff this morning and hopefully have a
new RC out for testing this afternoon.
Benjamin Bentmann wrote:
John Casey wrote:
Okay, I'm retracting this vote to fix:
MNG-4210
MNG-4213
As a suggestion, probably worth to consider merging MNG-4179 in from the
2.2.x
On 20/06/2009, at 2:29 AM, Brian Fox wrote:
This is probably a rare situation but does present itself like a
regression. On the flip side, I would love to be able to enable
pre-emptive authentication but I would want to do it per server. This
would have the effect of halving the requests and up
John Casey wrote:
Okay, I'm retracting this vote to fix:
MNG-4210
MNG-4213
As a suggestion, probably worth to consider merging MNG-4179 in from the
2.2.x branch as well.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...
Okay, I'm retracting this vote to fix:
MNG-4210
MNG-4213
This puts wagon -beta-6 in the release train for Maven 2.2.0. I'll stage
them both simultaneously for an RC period, then try to do the releases.
-john
John Casey wrote:
Hi,
I'm opening a new vote for Maven 2.2.0 after closing:
http:
John Casey schrieb:
> This would be because of the recent addition of log4j, which is now
> shaded into the Maven binary (bundled with a changed package structure
> to keep it out of the way of plugins' own log4j dependencies).
> httpclient is using log4j because it's available, but log4j doesn'
Ok John and I looked into this further and here's what we found:
Maven 2.2.0 (with the new wagon) is sending preemptive authentication.
The reason it failed for me is I had a server entry for Nexus that
matched my mirror setting. The auth in there was for another Nexus and
not for my personal one.
Can you elaborate on the errors? Do we need to file a JIRA for it?
Brian Fox wrote:
I'm having trouble getting this version to work against my Nexus
instance. I keep getting authorization errors even though it's setup
for anonymous. Switching back to 2.1.0 works immediately.
On Fri, Jun 19, 200
John Casey wrote:
but unless it's completely hiding all output I'd say we should fix it in 2.2.1.
+1, btw I already created a JIRA [0] for this:
Benjamin
[0] http://jira.codehaus.org/browse/MNG-4210
-
To unsubscribe, e-m
I'm having trouble getting this version to work against my Nexus
instance. I keep getting authorization errors even though it's setup
for anonymous. Switching back to 2.1.0 works immediately.
On Fri, Jun 19, 2009 at 10:36 AM, Jörg Schaible wrote:
> Hi John,
>
> John Casey wrote:
>
>> This would be
Hi John,
John Casey wrote:
> This would be because of the recent addition of log4j, which is now
> shaded into the Maven binary (bundled with a changed package structure
> to keep it out of the way of plugins' own log4j dependencies).
> httpclient is using log4j because it's available, but log4j
This would be because of the recent addition of log4j, which is now
shaded into the Maven binary (bundled with a changed package structure
to keep it out of the way of plugins' own log4j dependencies).
httpclient is using log4j because it's available, but log4j doesn't have
a configuration incl
John Casey schrieb:
> Hi,
>
> I'm opening a new vote for Maven 2.2.0 after closing:
>
> http://jira.codehaus.org/browse/MNG-4169
> http://jira.codehaus.org/browse/MNG-4207
>
> All URLs below have been updated where appropriate.
>
> ---
This version displays
log4j:WARN No appenders cou
+1
Tested on some little oss project plus some corp. ones without any issue.
Did not test the release cycle yet.
/Paul
Le jeudi 18 juin 2009 02:50:02, John Casey a écrit :
> Hi,
>
> I'm opening a new vote for Maven 2.2.0 after closing:
>
> http://jira.codehaus.org/browse/MNG-4169
> http://jir
+1
-Lukas
John Casey wrote:
Hi,
I'm opening a new vote for Maven 2.2.0 after closing:
http://jira.codehaus.org/browse/MNG-4169
http://jira.codehaus.org/browse/MNG-4207
All URLs below have been updated where appropriate.
---
Okay, it looks like there haven't been many problems wit
+1 [non-binding]
Tested with a couple of multi-module projects, especially looking at MNG-4140.
John Casey schrieb:
Hi,
I'm opening a new vote for Maven 2.2.0 after closing:
http://jira.codehaus.org/browse/MNG-4169
http://jira.codehaus.org/browse/MNG-4207
All URLs below have been updated wh
+1 tested the usual build/test cycle on a few projects an all works fine. Did
not test releases though!.
LieGrue,
strub
--- Benjamin Bentmann schrieb am Do, 18.6.2009:
> Von: Benjamin Bentmann
> Betreff: Re: [VOTE] Maven 2.2.0 (Second Attempt)
> An: "Maven Developers
List
> Subject: Re: [VOTE] Maven 2.2.0 (Second Attempt)
>
> John Casey wrote:
>
>> https://repository.apache.org/content/repositories/maven-staging-022/
>
> +1
>
>
> Benjamin
>
> -
> To
+1 [non-binding]
-Original Message-
From: Benjamin Bentmann [mailto:benjamin.bentm...@udo.edu]
Sent: Thursday, June 18, 2009 11:36 AM
To: Maven Developers List
Subject: Re: [VOTE] Maven 2.2.0 (Second Attempt)
John Casey wrote:
> https://repository.apache.org/content/repositories/ma
John Casey wrote:
https://repository.apache.org/content/repositories/maven-staging-022/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
+1
Tested on Maven doxia, wagon, release and some plugins and Incubator shindig
Cheers,
Vincent
2009/6/17, John Casey :
> Hi,
>
> I'm opening a new vote for Maven 2.2.0 after closing:
>
> http://jira.codehaus.org/browse/MNG-4169
> http://jira.codehaus.org/browse/MNG-4207
>
> All URLs below
+1
2009/6/18 Daniel Kulp
>
> +1
>
> Tested with CXF and some of the profiles that don't work correctly with
> 2.1.0
> work fine with 2.2.0.
>
> Dan
>
>
> On Wed June 17 2009 8:50:02 pm John Casey wrote:
> > Hi,
> >
> > I'm opening a new vote for Maven 2.2.0 after closing:
> >
> > http://jira.cod
+1
Tested with CXF and some of the profiles that don't work correctly with 2.1.0
work fine with 2.2.0.
Dan
On Wed June 17 2009 8:50:02 pm John Casey wrote:
> Hi,
>
> I'm opening a new vote for Maven 2.2.0 after closing:
>
> http://jira.codehaus.org/browse/MNG-4169
> http://jira.codehaus.or
Hi,
I'm opening a new vote for Maven 2.2.0 after closing:
http://jira.codehaus.org/browse/MNG-4169
http://jira.codehaus.org/browse/MNG-4207
All URLs below have been updated where appropriate.
---
Okay, it looks like there haven't been many problems with the latest RC
of Maven 2.2.0. S
*SIGH*
It looks like we have a bug in the currently staged Maven 2.2.0 version.
The problem seems to stem from the fact that the non-lightweight http
wagon depends on log4j. Since log4j is shaded into the eventual Maven
distribution, the log4j properties file seems to lose track of the
change
+1 [non-binding]
works fine for me,
Nicolas
2009/6/16 Reinhard Nägele
> +1 [non-binding]
>
>
> John Casey schrieb:
>
> Hi,
>>
>> Okay, it looks like there haven't been many problems with the latest RC of
>> Maven 2.2.0. So, I'd like to put it up for a vote.
>>
>> We've solved 23 issues for this
Yes it's just a new thread about the eclipse:eclipse plugin.I replied ;-)
Arnaud
On Tue, Jun 16, 2009 at 8:46 AM, Brett Porter wrote:
>
> On 16/06/2009, at 4:37 PM, Andrei Solntsev wrote:
>
> Hi,
>> Have you seen this post about recent release of maven-eclipse-plugin?
>> http://twasink.net/bl
On 16/06/2009, at 4:37 PM, Andrei Solntsev wrote:
Hi,
Have you seen this post about recent release of maven-eclipse-plugin?
http://twasink.net/blog/2009/06/this-is-why-maven-gives-me-the-shits/
Guys are a little bit frustrated saying " Why, Maven developers?
Why? Why are you releasing any ne
this. "
Andrei Solntsev
-Original Message-
From: Reinhard Nägele [mailto:reinhard.naeg...@mgm-tp.com]
Sent: Tuesday, June 16, 2009 9:33 AM
To: Maven Developers List
Subject: Re: [VOTE] Maven 2.2.0
+1 [non-binding]
John Casey schrieb:
> Hi,
>
> Okay, it looks like there haven&#
+1 [non-binding]
John Casey schrieb:
Hi,
Okay, it looks like there haven't been many problems with the latest
RC of Maven 2.2.0. So, I'd like to put it up for a vote.
We've solved 23 issues for this release:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&ve
+1 [non-binding]
-Original Message-
From: John Casey [mailto:jdca...@commonjava.org]
Sent: Monday, June 15, 2009 2:30 PM
To: Maven Developers List
Subject: [VOTE] Maven 2.2.0
Hi,
Okay, it looks like there haven't been many problems with the latest RC
of Maven 2.2.0. So, I'
Hi,
Okay, it looks like there haven't been many problems with the latest RC
of Maven 2.2.0. So, I'd like to put it up for a vote.
We've solved 23 issues for this release:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15103
You can download the source
53 matches
Mail list logo
