Following updates posted earlier today the gump builds for almost all of the avalon codebase is working. Two subproject were failing yesterday - avalon-util-extension-impl and fortress. I've fixed the extensions impl project (an error in the project name property). This leaves fortress.
Digging into the fortress build procedures raises a couple of concerns. It appears to be using custom ant targets to generate multiple artifacts out of a single maven project (which is not the way to use maven). In addition the gump based build uses a different script which is assuming a maven style code structure and as a consequence the gump build is failing.
My immediate conclusion is that we need to rip out all of the custom maven.xml stuff - and turn it into a set of typical subprojects - then setup a dedicated avalon-legacy gump process that grabs a tagged branch and builds using classic ant.
WDYT?
Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
