I am thinking whether there is maven plugin would help us to repackge the tomcat jar file to include our changes, so that we do not need to maintain the whole Tomcat source codes, maybe just need to keep a few files.
I don't have a good solution to this, but reconstructing our tomcat project every week or two to pick up tomcat updates still seems to me like the easiest way to get maven-usable snapshots from tomcat.On Dec 1, 2009, at 9:07 PM, Ivan wrote:Being different with 6.0.20, Tomcat trunk is under development, how to keep our codes are consistent with Tomcat's , Or, we just keep it temporarily for integrating our own patches ?
Do you have any ideas for another way to do this?thanksdavid jencks2009/12/2 David Jencks <firstname.lastname@example.org>
I wonder if we should figure out a way to use tomcat trunk rather than our modifiec 6.0,20. They are presumably making some progress on servlet 3.0 and there are definitely some fixes we could use.... for instance the recent problem I fixed where jasper assumed all classloaders are URLClassLoaders was already fixed more thoroughly in tomcat trunk.
If I was to do this I guess I'd set up a project like our 6.0.20 external project and build it with maven. I think this is a viable approach but hope I'm not the one to set it up :-)