On Mon, 15 Mar 2004, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
I am splitting excalibur-event into "api" and "impl" as this is how the build system is (and been for a long time). But "cocoon" is depending on "excalibur-event", so how should I go about fixing their <depend>s ??
Send a patch to their dev list and tell them that their project is going to be dropped by Gump until your patch has been applied. 8-)
and if you want to be a nice guy, keep around a "delegating" <project/>. For example,
http://cvs.apache.org/viewcvs.cgi/*checkout*/avalon/buildsystem/gump-integration/project/avalon.xml
has one. You can also have something like
<!-- don't use this one!!!
Migrate to depending on project-api and project-impl instead... -->
<project name="project">
<depend project="project-api" inherit="jars"/>
<depend project="project-impl" inherit="jars"/>
</project>inherit="jars" makes it appear that "project" actually produces the jars produced by "project-api" and "project-impl". It's a bit of a dirty trick, and the downside is that these things just lay around and clutter things up.
In any case, get in touch with the dependees of the project, which are listed in the gump output:
http://lsd.student.utwente.nl/gump/avalon-excalibur/excalibur-logger.html#Project+Dependees
as always, someone should probably be documenting questions+answers on the wiki :-D
-- cheers,
- Leo Simons
----------------------------------------------------------------------- Weblog -- http://leosimons.com/ IoC Component Glue -- http://jicarilla.org/ Articles & Opinions -- http://articles.leosimons.com/ ----------------------------------------------------------------------- "We started off trying to set up a small anarchist community, but people wouldn't obey the rules." -- Alan Bennett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
