Extending existing mojo's doesn't work very well, because the parameters for the extended mojo are not injected.
Do you really need to subclass ? Can't you just write an additional mojo and bind that to the install phase, next to the ordinary install ? And when you have the OBR plugin, would you mind sharing it :) ? Tom On 2/17/07, Tim Moloney <[EMAIL PROTECTED]> wrote:
Wendy Smoak wrote: > On 2/17/07, Tim Moloney <[EMAIL PROTECTED]> wrote: > >> I'd like to add a little extra functionality to the maven-install-plugin >> (create/update an xml file based on the jar being installed). > > Does your file go inside the jar, beside it in the repository, or > somewhere else? > > Maven already writes and updates the xml metadata files in its > repositories, so there should be some code to borrow if that's what > you need to do. > The file would be in the root of the local repository (~/.m2/repository/repository.xml) and allow the local repository to also be an OSGi bundle repository (OBR). I know that I can get things working by copying existing code into my plugin. However, that's not the best implementation from a maintenance point of view. I was hoping to write a plugin that called the code in maven-install-plugin (to keep present and future compatibility) and just add my little bit. Tim --------------------------------------------------------------------- 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]
