2008/12/18 Mansour <mansou...@yahoo.com> > > Put the worker classes in a separate jar, leave the classes extending > > AbstractMojo in the plugin, and have the plugin depend on the worker > classes > > jar. > > > Where does my new mojo fits ? If I separate the logic in a jar artifact > (which by the way the author of the docbkx did a great job on that) and > leave the old mojo, then where does the modification goes? In a new > mojo, in the original one ? in the pom (set the default values) ?
In a new mojo, or in a new jar that depends on the old mojo's worker jar, and then you write a mojo that uses your new jar > > > Examples of this pattern would be in some of the plugins (I suspect the > > enforcer and resources plugins would be good examples) > > > I am looking into this now > http://maven.apache.org/plugins/maven-enforcer-plugin/usage.html , and > will check out the source soon. > > -Stephen > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
