Kalle,
I hadn't thought of the version bit .. I think that sounds good. I will
try to get that working.
One problem is that (while I know I should) I haven't had the time to
create our own internal maven repository yet. We currently include a
bunch of jars via <scope>system ... ugly, I know but time hasn't allowed
an alternative - yet!
Thanks, p.
On 21/02/2012 10:10 AM, Kalle Korhonen wrote:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
