On Mon, Feb 20, 2012 at 2:47 PM, Paul Stanton <p...@mapshed.com.au> wrote: > I have multiple tapestry projects which all need to have the patches > applied, and so far the only reliable method I can find is to include them > in each projects source tree. I am finding it difficult to ensure that the > patch is applied when it is contained in its own jar since this method of > patching depends on the classloader and the order the jars are loaded etc. > The other alternative is to create a patched copy of tapestry-core.jar, and > then exclude tapestry-core from the pom, however this seems ugly.
Why would this be ugly? I have lots of libraries with patched up versions for my company's use, each deployed to our internal Maven repo with an additional version identifier, such as 5.1.0.5-mycompany-1. You don't have to exclude anything. If you specify that specific version in your application pom, the nearest version resolution takes care of including that version as a dependency, rather than some other version via transitive dependency. Kalle --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
