Hi Paul,

> 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.

Sounds tricky - are you saying when you include the source tree in your project 
you don't have to do the self-containted jar of patches?  And if you don't have 
the source-tree approach you need to play around with the patched jar with a 
different load-order?  I'm not savvy in tapestry internals.  It sounds like a 
lot of extra work.

> 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.
> 
> How have the rest of you approached this problem?

Could you just build your own (patched) tapestry-core.jar then host your own 
maven repo?  I've set up archiva (http://archiva.apache.org) and it works.  I 
don't know the ins and outs of it in depth, nor it's shortcomings, but it does 
what I need it to.  This way you can point your poms to use your repository for 
all the projects.

> I'm not looking for a debate on the need to apply patches - I don't think 
> this is a shortcoming of tapestry in particular, but it is a problem I need 
> to solve.

I do the same for a bunch of telco stuff - I have my own svn for what I know 
works - I may have to update my svn versions 10 times in the year.  It's not 
maven, but a bunch of bash installation scripts that save me the thought of 
what to do next (well commented too :) - in the same way, having your own 
pom/jar/repo setup, you would free your mind of those patching peculiarities - 
perhaps (excuse the alliteration) and just no-brainer build it together.


> Thanks for your help, Paul.


Hope it helps - 
Cheers
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to