You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by robert burrell donkin <ro...@blueyonder.co.uk> on 2006/02/17 00:09:39 UTC
[logging] please check release candidate 5
i'm now reasonably satisfied with this release candidate. if there's
anyone with a wondoz box and a few cycles, i'd be very grateful if you
could check the EOLs on the zips (source and binary).
my plan is to leave it a day or two to see whether anyone here can find
any problems.
i'll then cut a release branch and an ALPHA1 release for general
criticism. my plan is to use a series of releases (ALPHA, BETA then FC)
modelled on the HTTPD/tomcat/struts release style to allow a bigger
chance for feedback. this will be a change for the commons so we'll see
how it's received. i'll write this up on the wiki a little later.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] please check release candidate 5
Posted by Simon Kitching <sk...@apache.org>.
On Fri, 2006-02-17 at 08:44 +0100, Boris Unckel wrote:
> Good Morning,
> Simon Kitching wrote:
> > At some point I think it would be a good idea to post a notice to the
> > tomcat dev list, as the subscribers there are likely to (a) care about
> > JCL, and (b) have some interesting apps to test it with.
> >
> > Maybe jboss would also be good to contact, as they have had problems
> > with JCL in the past. I believe they actually have special-case handling
> > for JCL in their classloaders.
>
> I can test on WSAD and WAS if there is interest. We have situations
> where a company propietary logging
> framework fails, I can reproduce them with JCL.
Yes please!
If there are any issues (hopefully there won't be), please enable JCL's
diagnostic output and include that in the bugreport or email. Details on
enabling diagnostic output are in the release notes.
Cheers,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] please check release candidate 5
Posted by Boris Unckel <b....@gmx.net>.
Hello,
@Robert and Simon: I have sent this eMail to your personal adresses as
BCC because I do not know if any file attachments are
allowed on the list.
robert burrell donkin wrote:
>> I can test on WSAD and WAS if there is interest. We have situations
>> where a company propietary logging
>> framework fails, I can reproduce them with JCL.
>>
>
> yes please :)
>
> thanks for all the help
>
> - robert
>
> Yes please!
>
> If there are any issues (hopefully there won't be), please enable JCL's
> diagnostic output and include that in the bugreport or email. Details on
> enabling diagnostic output are in the release notes.
>
> Cheers,
>
> Simon
I have started my tests and the first one led to an error.
Environment: WSAD 5.1
Simple Enterprise Project, including one EAR and depending EJB and WAR
project.
EAR includes commons-logging...jar and WAR with WEB-INF/lib includes
commons-logging...jar
The Server is set to classloader multiple, ear is in Module - ParentLast
mode, war (as child of the ear) is in ParentLast mode.
For those who do not know WSAD/WAS:
- Module: An child WAR of an EAR has its own classloader, which is child
of the EAR's classloader
- Application: EAR and WAR share the same classloader, most times the
JAR of WEB-INF/lib wins (not documented, my own subjective observation)
There is just ONE difference between the working and the error version:
Working: JVM parameter
-Dorg.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl
is set
Error: There is no -Dorg.apache.commons.logging.LogFactory specified
See ZIP with System.out / System.err for details.
What tests and test combinations do you expect? There are dozens..
Server; EAR; WAR
No special loglib, classloader multiple; module, parentLast,
commons-logging.jar on path; parentLast commons-logging.jar on path
No special loglib, classloader multiple; module, parentLast,
commons-logging.jar on path; parentLast
commons-logging.jar on path, classloader multiple; module, parentLast, ;
parentLast
No special loglib, classloader multiple; module, parentLast,
commons-logging.jar on path; parentFirst commons-logging.jar on path
No special loglib, classloader multiple; module, parentLast,
commons-logging.jar on path; parentFirst
commons-logging.jar on path, classloader multiple; module, parentLast ;
parentFirst
No special loglib, classloader multiple; module, parentFirst,
commons-logging.jar on path; parentFirst commons-logging.jar on path
No special loglib, classloader multiple; module, parentFirst,
commons-logging.jar on path; parentFirst
commons-logging.jar on path, classloader multiple; module, parentFirst ;
parentFirst
===
No special loglib, classloader single; module, parentLast,
commons-logging.jar on path; parentLast commons-logging.jar on path
No special loglib, classloader single; module, parentLast,
commons-logging.jar on path; parentLast
commons-logging.jar on path, classloader single; module, parentLast, ;
parentLast
No special loglib, classloader single; module, parentLast,
commons-logging.jar on path; parentFirst commons-logging.jar on path
No special loglib, classloader single; module, parentLast,
commons-logging.jar on path; parentFirst
commons-logging.jar on path, classloader single; module, parentLast ;
parentFirst
No special loglib, classloader single; module, parentFirst,
commons-logging.jar on path; parentFirst commons-logging.jar on path
No special loglib, classloader single; module, parentFirst,
commons-logging.jar on path; parentFirst
commons-logging.jar on path, classloader single; module, parentFirst ;
parentFirst
Regards
Boris
Re: [logging] please check release candidate 5
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On Fri, 2006-02-17 at 08:44 +0100, Boris Unckel wrote:
> Good Morning,
> Simon Kitching wrote:
> > At some point I think it would be a good idea to post a notice to the
> > tomcat dev list, as the subscribers there are likely to (a) care about
> > JCL, and (b) have some interesting apps to test it with.
> >
> > Maybe jboss would also be good to contact, as they have had problems
> > with JCL in the past. I believe they actually have special-case handling
> > for JCL in their classloaders.
>
> I can test on WSAD and WAS if there is interest. We have situations
> where a company propietary logging
> framework fails, I can reproduce them with JCL.
yes please :)
thanks for all the help
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] please check release candidate 5
Posted by Boris Unckel <b....@gmx.net>.
Good Morning,
Simon Kitching wrote:
> At some point I think it would be a good idea to post a notice to the
> tomcat dev list, as the subscribers there are likely to (a) care about
> JCL, and (b) have some interesting apps to test it with.
>
> Maybe jboss would also be good to contact, as they have had problems
> with JCL in the past. I believe they actually have special-case handling
> for JCL in their classloaders.
I can test on WSAD and WAS if there is interest. We have situations
where a company propietary logging
framework fails, I can reproduce them with JCL.
Regards
Boris
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] please check release candidate 5
Posted by Simon Kitching <sk...@apache.org>.
On Thu, 2006-02-16 at 23:09 +0000, robert burrell donkin wrote:
> i'm now reasonably satisfied with this release candidate. if there's
> anyone with a wondoz box and a few cycles, i'd be very grateful if you
> could check the EOLs on the zips (source and binary).
>
> my plan is to leave it a day or two to see whether anyone here can find
> any problems.
>
> i'll then cut a release branch and an ALPHA1 release for general
> criticism. my plan is to use a series of releases (ALPHA, BETA then FC)
> modelled on the HTTPD/tomcat/struts release style to allow a bigger
> chance for feedback. this will be a change for the commons so we'll see
> how it's received. i'll write this up on the wiki a little later.
At some point I think it would be a good idea to post a notice to the
tomcat dev list, as the subscribers there are likely to (a) care about
JCL, and (b) have some interesting apps to test it with.
Maybe jboss would also be good to contact, as they have had problems
with JCL in the past. I believe they actually have special-case handling
for JCL in their classloaders.
Cheers,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] please check release candidate 5
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
On Sat, 2006-02-18 at 06:21 +0000, Niall Pemberton wrote:
> I downloaded both the src and binary zip files and opened up a few of the
> *.java, *.html and *.txt files with Notepad on windows - all looked good, no
> problem with the EOLs. Is that enough of a check or did you want something
> more?
i used subversion to do the conversions for the source. 'svn export
--native-eols ...' exports the source and converts the line endings to
that specified. AIUI it's added in subversion 1.3.
i wanted to double check that it worked ok.
thanks
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [logging] please check release candidate 5
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
I downloaded both the src and binary zip files and opened up a few of the
*.java, *.html and *.txt files with Notepad on windows - all looked good, no
problem with the EOLs. Is that enough of a check or did you want something
more?
Niall
----- Original Message -----
From: "robert burrell donkin" <ro...@blueyonder.co.uk>
Sent: Thursday, February 16, 2006 11:09 PM
> i'm now reasonably satisfied with this release candidate. if there's
> anyone with a wondoz box and a few cycles, i'd be very grateful if you
> could check the EOLs on the zips (source and binary).
>
> my plan is to leave it a day or two to see whether anyone here can find
> any problems.
>
> i'll then cut a release branch and an ALPHA1 release for general
> criticism. my plan is to use a series of releases (ALPHA, BETA then FC)
> modelled on the HTTPD/tomcat/struts release style to allow a bigger
> chance for feedback. this will be a change for the commons so we'll see
> how it's received. i'll write this up on the wiki a little later.
>
> - robert
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org