Jeremias,
I've removed the reference to retroweaver to fix this bug.
What I tried to do was to add the "verify" task of retroweaver, not
the "weave" task. Verify will check if all the classes are available
in 1.4, which is something we should definitely to, even for the
current trunk. It was not my intention to do any actual weaving.
My mistake here was not to remove the reference, this happend because
I was doing these changes offline. In the build-file, as submitted,
the task was not actually used, just defined.
My main issue here is that I cannot replicate the error message: I've
tried JDK 1.4, 1.5, and 1.6, and never got this error message. Which
JDK / ant version does gump run with?
Max
Am 12.06.2008 um 15:16 schrieb Jeremias Maerki:
That's obviously Retroweaver that causes the failure here. The fix in
[1] is easy but: Max, why did you add retroweaver to Trunk while we
were
not yet in agreement if the experiment should be done in a branch or
not?
I clearly stated my preference.
[1] https://svn.apache.org/repos/asf/gump/metadata/project/xml-fop.xml
On 11.06.2008 17:24:11 Jeremias Maerki wrote:
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project xml-fop has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 33 runs.
The current state of this project is 'Failed', with reason 'Build
Failed'.
For reference only, the following projects are affected by this:
- xml-fop : XSL-FO (Formatting Objects) processor
<snip/>
BUILD FAILED
/srv/gump/public/workspace/xml-fop/build.xml:460: taskdef class
net.sourceforge.retroweaver.ant.RetroWeaverTask cannot be found
<snip/>
Jeremias Maerki
