I'm having a problem with the release plugin, BOMs in the reactor, and
Maven 3.x. I just uncovered the problem last night, and spent a good
part of today trying to narrow it down and verify that it isn't
something I'm doing wrong.
The issue is http://jira.codehaus.org/browse/MNG-4962
This will definitely have an effect on groups that are building large
project structures with BOMs to help coordinate versions.
I'm still trying to figure out what might be the best way to fix it, or
even to understand how I might go about fixing it at all (still don't
completely understand the root cause yet), but I'm happy to help where I
can.
On 1/5/11 4:20 PM, Benjamin Bentmann wrote:
Hi,
we're aiming at a bugfix release of Maven 3 in the next week and
following tradition we invite interested users in taking the RC for a
test drive in order to detect and fix potential regressions since
version 3.0.1 before the actual release of 3.0.2.
For the duration of the RC testing, sources and binaries are staged at:
https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0.2-RC1/
As usual, the changes since the previous release are listed in JIRA:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=16952
Thanks,
-The Maven Team
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.johnofalltrades.name/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
