I've disabled the test module that uses Cactus until we can fix this. I'm not very familiar with what Gump is doing and could use some help rectifying this. We specify the version of Cactus to use in the POM and the module does build locally. What's going on inside Gump that would cause it to use a different version? Is it trying to build with an unstable version of Cactus rather the version we specify?
The normal "package" goal would build the jar and not run the integration tests. Alternatively, if Gump can supply a maven profile we could create one that skipped this module or the tests. Both seem to defeat the point though. Thanks Jeremy On Jul 9, 2010, at 3:12 AM, Stefan Bodewig wrote: > Hi, > > this started failing when you added Cactus to the mix, apparently > because the version of Cactus used is incompatible with some JDOM > changes in trunk or something like this. Unfortunately getting Cactus > to build inside Gump is a long shot. > > Is there any goal for the standard taglibs build we could use that would > only create the jar but not run the cactus:cactifywar plugin so > downstream dependencies of the standard taglibs build (Jelly) could be > built inside Gump until we get the rest resolved? I offer to disable > nagging in exchange ;-) > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
