Hi, I could use a hand to figure out what is happening here.
It looks as if a Velocity macro definition inside the used version of Doxia was parsed during Checkstyle and this macro definition was invalid according to the trunk version of Velocity that is being used. Unfortunately I have no idea why and how Checkstyle and Doxia play together, I don't even manage to figure out which version of Doxia the build is using. We do have a mixture of Gump built artifacts (checkstyle, velocity, all of commons, jdom and a lot more) and artifacts that are the real versions you've asked for (all plugins, most of maven itself, all plexus stuff, doxia and more). Short term: is there a way to generate the Cargo jars without running Checkstyle and triggering the problem? Longer term it would be nice to know whether the macro definition really is broken or whether the build is triggering a bug in Velocity's trunk. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
