Just need one more +1 binding... -Dan -----Original Message----- From: Brett Porter <[EMAIL PROTECTED] Date: Friday, Sep 26, 2008 7:38 am Subject: Re: [VOTE] Release maven-reactor-plugin 1.0 (take 2) To: Reply- "Maven Developers List" <[email protected]>To: "Maven Developers List" <[email protected]>
+1 it is working well for me now > >On 24/09/2008, at 6:27 AM, Dan Fabulich wrote: > >> > Fixed the issue Brett found (I don't know why it worked at all on my > machine), as well as tossing in a quick new feature MREACTOR-5 which > allows you to resume a reactor:make build. > >> Also, this time I made sure I deployed the 1.0 site. > >> ---------- Forwarded message ---------- > Date: Tue, 16 Sep 2008 18:53:41 -0700 (PDT) > From: Dan Fabulich <[EMAIL PROTECTED]> > Reply-To: Maven Developers List <[email protected]> > To: Maven Developers List <[email protected]> > Subject: [VOTE] Release maven-reactor-plugin 1.0 > >> > 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 were released as > part of 2.1.0-M1. [edited in take 2] > >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
