> The Require OS Version rules docs is using <goal>os</goal> instead of
><goal>require</goal> (or <goal>require-once</goal>). Good catch. I'll make that change. > Is it close to time for a release of 1.0-alpha-1 of this puppy yet? Getting there. I want to explore Jerome's comments about reports and a vistor pattern. I haven't spent a lot of time thinking about it, but I'm not sure how a visitor would help here. We really are only interested in the message coming back. A report mojo could catch all the rule results and report them. Comments? What am I missing? I don't want to do a release until we can be relatively sure the interface for the rules won't change. -----Original Message----- From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason Dillon Sent: Tuesday, April 03, 2007 3:51 PM To: Maven Developers List Subject: Re: maven-enforcer-plugin * * * Is it close to time for a release of 1.0-alpha-1 of this puppy yet? --jason On Apr 2, 2007, at 7:31 PM, Brian E. Fox wrote: > Ok, a little more refactoring. The Custom rules can now get to the > ExpressionEvaluator so they can get pretty much anything a plugin > could > get. The sites are updated to contain info about the standard rules > and > the custom rule creation: > http://maven.apache.org/plugins/maven-enforcer-plugin/ > http://maven.apache.org/shared/maven-enforcer-rule-api/index.html > > I'll let this linger for a day or so and then call a vote if nothing > turns up. > > Thanks, > Brian > > -----Original Message----- > From: Brian E. Fox [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 29, 2007 11:59 PM > To: Maven Developers List > Subject: RE: maven-enforcer-plugin > > I reimplemented the enforcer plugin along the lines of Jason D's > idea[1] > and I think this is a much more extensible solution. The rules now > implement a common interface in shared/maven-enforcer-rule-api and > users > will be able to inject their own custom rules. By defining the > interface > external to the plugin, the Lint idea that JVZ put out[2] should be > able > to invoke these rules, as will IDEs. > > Please take a look at the site to see how the plugin works and provide > any suggestions. I still need to document how to create your own rules > and inject them, but I believe everything else is covered. A > snapshot of > 1.0-alpha-1 has also been deployed for testing. (I believe Geronimo is > already using it) > > http://maven.apache.org/plugins/maven-enforcer-plugin (just deployed, > may take a while to refresh) > > [1] > http://www.nabble.com/maven-enforcer-plugin- > tf3431452s177.html#a9565974 > [2] http://www.nabble.com/Maven-Lint-tf3462956s177.html#a9661545 > > -----Original Message----- > From: Brian E. Fox [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 20, 2007 12:05 AM > To: Maven Developers List > Subject: maven-enforcer-plugin > > There is a new plugin that I'd like to get some feedback on, > particularly on non-windows os's and the unit tests. > > > > The maven-enforcer-plugin picks up where <prerequisites> leaves off > and > allows control over the maven, jdk and os versions of a build. > > > > This plugin was initially conceived here: > > http://www.nabble.com/Control-of-maven-using-prerequisites- > tf3231437s177 > .html#a8979318 > > And here: > > http://www.nabble.com/Why-is-prerequisites-not-inherited-- > tf3236197s177. > html#a9016296 > > > > 1.0-alpha-1-SNAPSHOT is deployed and the site is here: > http://maven.apache.org/plugins/maven-enforcer-plugin/ (just > deployed so > give it a little bit to completely update) > > > > If all goes well and no major issues are uncovered, then I think it's > ready for staging and a vote. > > > > Thanks, > > Brian > > > > > > > > > > > --------------------------------------------------------------------- > 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] > --------------------------------------------------------------------- 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]
