Thank you Stephen, hum, Let's make sure I got the idea. Every plugin consist of mojo classes. So in this case, I start my plugin and set the modified docbokx plugin as a depency (jar depency), then I extend the mojos I want to modify and over ride them by setting the default values I need. In order to do this, I need to move the mojos from the docbokx into a separate jar file. Is this right ?
Or, download the source for the docbokx plugin, and modify it. Will this be easier? Which approach you will go for? Stephen Connolly wrote: > > The idea is to develop plugins so that most (if not all) the work is > performed in a regular jar artifact... that way, to extend the plugin you > just depend on the jar file not the plugin. > > What you therefore want to do is ensure that the plugin you need to extend > is refactored so that 99.9% of the code in the mojo is moved into a separate > module, then you just depend on that module. > > >> Thank you. >> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
