Hi Dan,
The plugin is great and I'm in favour of the release. I checked all
the source and binaries and seems ready. The site seems to be for 1.1-
SNAPSHOT though.
However, I can't get 1.0 to run reactor:make-scm-changes, with this
error:
java.lang.NoClassDefFoundError: org/codehaus/plexus/util/xml/
XmlStreamReader
at
org
.apache
.maven
.scm
.provider
.svn
.svnexe
.command
.SvnCommandLineUtils.getBaseSvnCommandLine(SvnCommandLineUtils.java:98)
I've seen this before but don't recall the root cause (it's the
conflict between plexus-utils 1.1 in SCM and core I think) - anyone
else know? Occurs with both 2.0.9 and 2.1.0-M1, tried on Jetty trunk,
Continuum and Archiva.
If I add a dependency on plexus-utils 1.5.6 in the reactor plugin, it
works again.
Thanks,
Brett
On 17/09/2008, at 11:53 AM, Dan Fabulich wrote:
This plugin can build a subset of interdependent projects in a
reactor. It should be useful in large reactor builds that include
irrelevant stuff you're not working on.
http://maven.apache.org/plugins/maven-reactor-plugin/
A few important notes:
* This is maven-reactor-plugin's first official release. I know
it's traditional for us to call the first few releases 1.0-alpha-X
for a while, but it can often be difficult to decide when to drop
the "-alpha" qualifier, and I don't think very many people actually
like that old tradition. :-)
* One weird thing about the maven-reactor-plugin is that three of
its goals (reactor:make, reactor:make-dependents, reactor:resume)
are now features in the maven-2.1.x branch; they will presumably get
released as part of 2.1.0-M2.
I still think this plugin is worth releasing, for three reasons:
1) reactor:make-scm-changes will probably never become part of the
Maven core, and probably should never, so at least one goal has long
term value.
2) While I'd expected most people to use this goal from the command-
line, it will also work wired up as part of a POM, e.g. as the
default goal for particular profiles. The new core features are
command-line only.
3) A lot of people are on 2.0 and may be on 2.0 for a while yet
(even if we release 2.1 very quickly).
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11831&status=1
The biggest remaining issue is MREACTOR-1. It's pretty bad, but I
don't think it should hold up a 1.0 release.
http://jira.codehaus.org/browse/MREACTOR-1
Staging repo:
http://people.apache.org/~dfabulich/staging-repo/maven-reactor-plugin/
Staging site:
http://maven.apache.org/plugins/maven-reactor-plugin/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
