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,
Hey, you're doing great work pulling the quality of Maven releases
up... no need to apologise
-Stephen
2009/6/26 John Casey jdca...@commonjava.org:
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
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
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:
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:
*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
