You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Stefan Bodewig <bo...@apache.org> on 2005/01/20 13:43:37 UTC
[GUMP] cocoon and related failures
Hi all,
the Cocoon build failure looks as if you better used logging-log4j-12
instead of logging-log4j as dependency.
Also currently the paths to itext, chaperon, deli and
daisy-htmlcleaner you declare in your descriptor seem to be wrong.
Cheers
Stefan
Re: [GUMP] cocoon and related failures
Posted by Ceki Gülcü <ce...@qos.ch>.
At 07:11 PM 1/20/2005, Curt Arnold wrote:
>This looks like an unintentional (or at least undiscussed) break due to
>the packaging of log4j. I would discourage Cocoon from redirecting to
>logging-log4j-12 until the log4j project has had a chance to discuss the issue.
It was an unintentional breakage which was fixed even before we became
aware of its effect on Cocoon. In the next gump run the problem should
disappear.
Cheers,
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: [GUMP] cocoon and related failures
Posted by Ceki Gülcü <ce...@qos.ch>.
At 07:11 PM 1/20/2005, Curt Arnold wrote:
>This looks like an unintentional (or at least undiscussed) break due to
>the packaging of log4j. I would discourage Cocoon from redirecting to
>logging-log4j-12 until the log4j project has had a chance to discuss the issue.
It was an unintentional breakage which was fixed even before we became
aware of its effect on Cocoon. In the next gump run the problem should
disappear.
Cheers,
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
Re: [GUMP] cocoon and related failures
Posted by Curt Arnold <ca...@apache.org>.
This looks like an unintentional (or at least undiscussed) break due to
the packaging of log4j. I would discourage Cocoon from redirecting to
logging-log4j-12 until the log4j project has had a chance to discuss
the issue.
On Jan 20, 2005, at 6:43 AM, Stefan Bodewig wrote:
> Hi all,
>
> the Cocoon build failure looks as if you better used logging-log4j-12
> instead of logging-log4j as dependency.
>
> Also currently the paths to itext, chaperon, deli and
> daisy-htmlcleaner you declare in your descriptor seem to be wrong.
>
> Cheers
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
>
Re: [GUMP] cocoon and related failures
Posted by Curt Arnold <ca...@apache.org>.
This looks like an unintentional (or at least undiscussed) break due to
the packaging of log4j. I would discourage Cocoon from redirecting to
logging-log4j-12 until the log4j project has had a chance to discuss
the issue.
On Jan 20, 2005, at 6:43 AM, Stefan Bodewig wrote:
> Hi all,
>
> the Cocoon build failure looks as if you better used logging-log4j-12
> instead of logging-log4j as dependency.
>
> Also currently the paths to itext, chaperon, deli and
> daisy-htmlcleaner you declare in your descriptor seem to be wrong.
>
> Cheers
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org