You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Stephen McConnell <mc...@apache.org> on 2004/03/21 19:00:00 UTC
[gump] getting fortress sorted
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: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org