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 gene...@gump.apache.org.
Project xml-fop has an issue affecting its community integration.
This issue
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 gene...@gump.apache.org.
Project xml-fop has an issue affecting its community integration.
This issue
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
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
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
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
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
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]
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
Oh, I see. Forgive my ignorance of the various capabilities of
Retroweaver. In that case, I've added (rev667213) the necessary entries
to the Gump descriptor. You see, Gump is special. It doesn't just use
the bundled dependencies but always takes the newly created builds from
the projects FOP
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
My bad :(
Fix committed in the meantime.
Cheers
Andreas
On May 12, 2008, at 16:23, 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
12 matches
Mail list logo
