Here's a technique I received just the other day. I haven't done it yet, because the Maven port has been moved down my priority list by senior management, but it should work
> 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. Mark Eramo <[EMAIL PROTECTED]> wrote on 09/21/2007 02:07:26 PM: > Thanks for the links Robert. Based on the 2nd link, it looks like there > is some sort of patch for the plugin. > Is this something that I can install locally and if so, can you > recommend the best way to do this? > 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.
