[cle-release-team] 2.9.x: branch management update

Steve Swinsburg steve.swinsburg at gmail.com
Wed Mar 27 18:04:39 PDT 2013


You use System.err.println for normal logging?


On Thu, Mar 28, 2013 at 9:37 AM, Aaron Zeckoski <azeckoski at unicon.net>wrote:

> Neither, see the beginning of this thread.
> -AZ
>
>
> On Wed, Mar 27, 2013 at 6:29 PM, Steve Swinsburg
> <steve.swinsburg at gmail.com> wrote:
> > Ok. So are you using log4j or slf4j currently?
> >
> >
> > On Thu, Mar 28, 2013 at 9:22 AM, Aaron Zeckoski <azeckoski at unicon.net>
> > wrote:
> >>
> >> "Should" doesn't equal "does" unfortunately.
> >> EB registers providers from all over the place including from within
> >> components and within webapps (so it holds weak references to classes
> >> from lots of classloaders). It uses a similar technique for keeping
> >> track of the various internal bits and optional overrides as well.
> >> The bottom line is that when I tried to use commons logging, it held
> >> open the classloaders so EB could not shutdown and I got the wrong
> >> copies of classes sometimes. Either way, I gave up trying to solve
> >> that back in 2007. Maybe things are better these days but I will leave
> >> that as something for someone else to prove as I spent far too many
> >> hours on it.
> >>
> >> I'll note that everything worked fine if slf4j was used but sadly,
> >> this is not the case in Sakai.
> >> -AZ
> >>
> >>
> >> On Wed, Mar 27, 2013 at 6:11 PM, Steve Swinsburg
> >> <steve.swinsburg at gmail.com> wrote:
> >> > Something isn't right then. You should be able to log from the webapp
> >> > without classloader issues due to child-first, and you should be able
> to log
> >> > from the impl fine also. I thought it might be some odd setup that EB
> had?
> >> >
> >> > Most/all other tools can log fine in this manner.
> >> >
> >> >
> >> > Sent from my iPhone
> >> >
> >> > On 28/03/2013, at 9:01, Aaron Zeckoski <azeckoski at unicon.net> wrote:
> >> >
> >> >> Pretty much all the issues indicated in that link.
> >> >> -AZ
> >> >>
> >> >>
> >> >> On Wed, Mar 27, 2013 at 5:54 PM, Steve Swinsburg
> >> >> <steve.swinsburg at gmail.com> wrote:
> >> >>> What's the actual issue you are facing with JCL?
> >> >>>
> >> >>> Cheers
> >> >>> S
> >> >>>
> >> >>> Sent from my iPhone
> >> >>>
> >> >>> On 28/03/2013, at 5:53, Aaron Zeckoski <azeckoski at unicon.net>
> wrote:
> >> >>>
> >> >>>> For the EB uses, I cannot use the logger we normally use because of
> >> >>>> the issues with JCL and classloaders.
> >> >>>> http://articles.qos.ch/classloader.html
> >> >>>> Not sure about the other projects.
> >> >>>> -AZ
> >> >>>>
> >> >>>>
> >> >>>> On Wed, Mar 27, 2013 at 2:26 PM, Anthony Whyte <arwhyte at umich.edu>
> >> >>>> wrote:
> >> >>>>> Summary of 2.9.x branch management activities since Friday, 22
> >> >>>>> March.
> >> >>>>>
> >> >>>>> merged = 20
> >> >>>>> to merge = 13
> >> >>>>>
> >> >>>>> of these
> >> >>>>> merge conflicts encountered = 4
> >> >>>>> merge postponed until question is answered = 1
> >> >>>>> merge held up after code review = 1 [1]
> >> >>>>> ticket missing info (i.e., trunk revision number) = 1
> >> >>>>>
> >> >>>>> cheers,
> >> >>>>>
> >> >>>>> Anth
> >> >>>>>
> >> >>>>> [1] (SAK-22390 portal, log object vs System.err.println; we have a
> >> >>>>> log
> >> >>>>> object although after grepping CLE source a few projects such as
> EB,
> >> >>>>> LB,
> >> >>>>> portal, rwiki and samigo use System.err.println (174 instances)
> so I
> >> >>>>> can
> >> >>>>> hardly claim to be enforcing a rule, perhaps not even a best
> >> >>>>> practice with
> >> >>>>> respect to those projects.)
> >> >>>>>
> >> >>>>> _______________________________________________
> >> >>>>> cle-release-team mailing list
> >> >>>>> cle-release-team at collab.sakaiproject.org
> >> >>>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> >> >>>> _______________________________________________
> >> >>>> cle-release-team mailing list
> >> >>>> cle-release-team at collab.sakaiproject.org
> >> >>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> >> >>> _______________________________________________
> >> >>> cle-release-team mailing list
> >> >>> cle-release-team at collab.sakaiproject.org
> >> >>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> >> > _______________________________________________
> >> > cle-release-team mailing list
> >> > cle-release-team at collab.sakaiproject.org
> >> > http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> >>
> >>
> >>
> >> --
> >> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> >
> >
> >
> > _______________________________________________
> > cle-release-team mailing list
> > cle-release-team at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> >
>
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20130328/5cb74147/attachment-0006.html 


More information about the cle-release-team mailing list