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 <nicolas.del...@gmail.com> 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
