Hi all, I've been thinking about enforcer rules for some times. I think it would be a good thing to have a kind of enforcer-rules-incubator project somewhere that would encourage users share¢ralize their rules.
I personnally have already written rules that I think are not very specific to my organization (forbid putting <skip>true</skip> inside surefire conf, for example). I already considered pushing it somewhere, but even if creating a new project each time would indeed work, I really think it would be a bad thing for users (Maven ecosystem is already an enough diluted/large/complex one to add so many small projects). I think Maven community should encourage users to grow/contribute their rules to the standard rulesets, by creating for example an enforcer-incubator-rules project that would be a sandbox for rules that might become promoted in the standard ruleset when stable/interesting. WDYT? Cheers 2011/2/2 Brian Fox <[email protected]> > You could simply add a flag or alternate mojo to the dependency plugin > to allow it to fail. IIRC the analyze goal already does this. IOW it's > not a requirement that every mojo that fails a build be rolled into > the enforcer plugin. Failing that, you'd have to pull all the logic > out into a shared component. > > On Wed, Feb 2, 2011 at 8:16 AM, nicolas de loof > <[email protected]> wrote: > > Hi folks, > > > > I'd like to work on MENFORCER-19, > > org.apache.maven.plugin.dependency.AnalyzeDepMgt has all the necessary > code > > to create an EnforcerRule "EnforceDependencyManagement", but I wonder how > we > > should manage such code duplication. Copy/paste some hundred lines from > > dependency plugin into enforcer-rules is not very pleasant. > > > > Nicolas > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
