Craig,
Thanks for the immediate response. If possible, I would like the
warning text to include the following.
The problem is not caused by log4j but with the particular way
Struts-1.1-b2 was built. The problem will be solved in future releases
of Struts.
On an unrelated register, do you have the slides of your
"Recommendations for Java-Based Web Application Architectures" session
(ApacheCon 2001) in a format other than sdd?
At 08:47 11.09.2002 -0700, you wrote:
>Ceki,
>
>It was nothing wrong with Log4J -- the person who built the Struts release
>built commons-logging.jar from scratch, but without Log4J in his build
>environment (so the Log4J wrapper classes weren't included).
>
>The final Struts release will include final releases of the Commons
>packages it relies on, and we'll verify that everything is there.
>
>Craig
>
>
>On Wed, 11 Sep 2002, Ceki Gülcü wrote:
>
> > Date: Wed, 11 Sep 2002 16:33:36 +0200
> > From: Ceki Gülcü <[EMAIL PROTECTED]>
> > Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: Packaging error
> >
> >
> >
> > At http://jakarta.apache.org/builds/jakarta-struts/release/v1.1-b2/
> > one can read the following message:
> >
> > Log4J Users Please Note - A packaging error has been uncovered that
> > caused the copy of commons-logging.jar included in the Struts 1.1 Beta
> > 2 release to be built incorrectly. If you are using Log4J for your
> > logging needs, you will need to download the Commons Logging 1.0.1
> > release (convenient links are provided in the logging directory) and
> > replace your copy of commons-logging.jar with the one found in the
> > 1.0.1 release.
> >
> > What causes this packaging error? Could someone clarify this? Thank you
> > in advance,
--
Ceki
TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
