Hi All,
Like many of you, I've had to create a couple of local patches to get
certain things in tapestry working correctly.
For example, a fix for the DateField component
(https://issues.apache.org/jira/browse/TAP5-841) and a custom
AssetDispatcher to perform a 302 redirect instead of failing when the
application version is incorrect.
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.
How have the rest of you approached this problem?
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.
Thanks for your help, Paul.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
