> -----Original Message-----
> From: Adam R. B. Jack [mailto:[EMAIL PROTECTED]
> Sent: 24 August 2004 20:14
> To: Avalon Developers List
> Subject: RE: more on gump
>
> > Failures are merlin-cli, jmx-mx4j, and http-impl. The cli failure
> > appears to be related to the build referencing its own published
> > artifact before it is published (probably some tweaking of the build
> > file named).
>
> Do you need to use <work here?
>
> http://gump.apache.org/metadata/project.html#work
>
> BTW: Sometimes Ant (or maybe builds) drop paths from their classpath,
if
> they do not exist at start-up (even if they are populated before being
> used). For that we've used this in the past:
>
> http://gump.apache.org/metadata/project.html#mkdir
>
Actually the problem was related to magic. Basically the build file
contains a filter declaration
<x:filter feature="classpath" platform="windows"
prefix="%MERLIN_HOME%/system"
token="WINDOWS-CLI-CLASSPATH"/>
The above statement results in the creation of a MagicPath object
holding the full transitive dependencies for the project in question.
The default behavior of the path object is to resolve all entries in the
path against the repository. In this case the path entry included the
merlin-cli jar file which does not exist yet. I've just updated Magic
such that filter based acquisition of path objects defaults to
non-resolution of the jar files relative to the repository (because in
effect we only want the path as a string).
Changes should propagate though Gump before morning.
Cheers, Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
