(I saw your email on dev@ and waited for it to be posted on [EMAIL PROTECTED])
Here's how I patch Maven jars: download the code from svn apply patch modify pom to add -mycompany to version number ie 2.2.1.0-mycompany (use your own company name here) mvn install the file into your repo "lock down" the plugin in your poms to the new version <version>[2.2.1-mycompany]</version> Its generally a bad idea to specify a version that might actually be used in the future by the real maintainers of the plugin, that's why -mycompany is a good idea. You definitely don't want to just bump the version by 1. I believe this might be documented somewhere... the Wiki isn't working for me right now but I know we've discussed this here on users@ previously, so search the archives. Wayne On 9/19/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I'd like to implement a patch for maven-jar-plugin locally. How is that > done? I have created a local repository (file:// etc) for our custom > plugins and some "parent" poms shared by multiple artifacts. Should I > deploy my plugin there? Will it be preferred over the remote one if I do? > > The patch is already in jira (MJAR-30) so it's likely to be rolled up > eventually, but I'd prefer not to wait. Please note that I do not use any > tools, just maven from the command line. > > Thanks > Robert Egan > > This email message and any attachments may contain confidential, > proprietary or non-public information. The information is intended solely > for the designated recipient(s). If an addressing or transmission error > has misdirected this email, please notify the sender immediately and > destroy this email. Any review, dissemination, use or reliance upon this > information by unintended recipients is prohibited. Any opinions > expressed in this email are those of the author personally. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
