[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [stellation-res] Jakarta Commons Logging?
|
On Wednesday 17 July 2002 02:39 am, Ringo De Smet wrote:
> --- "Mark C. Chu-Carroll" <mcc@xxxxxxxxxxxxxx> wrote:
> > We're currently using Jakarta log4j v1.2rc1.
>
> Let's update this one to Log4J 1.2.5, a stable release version instead
> of a release candidate!
We definitely should. In the insanity surrounding getting the system
approved and set up on Eclipse, none of us had time to check on
library updates. Once the dust settles, there's a bunch of library
update work that we'll be doing. I'll try to check if 1.2.5 passes
ASAP, and if it does, we'll switch over. (If you could drop that into
bugzilla as a bug against the repos assigned to me, I'd appreciate
it. It would give me a reminder to do it, and who requested it.)
> > I have no objection to switching to the common logging framework,
> > and I can't imagine why anyone else would object (anyone who
> > does, please speak up!)
>
> I will wait some more before I start doing the work for other people to
> have time to respond.
>
> > I'm 99% certain that there won't be any objections to this change,
> > so please feel free to go ahead with the patch.
>
> Since the main repository is your Watson Stellation repo, and the CVS
> is a mirror of it, can I send patch files against the CVS repo? Or do I
> send the complete changed files?
I'm keeping the CVS repos up to date against the local Stellation
repos, so diffs against the CVS will be fine.
The core, ui, and model projects are up to date. I made a mistake
in handling the mirroring of misc that needs some fix-up, so that's
a day or two behind. (The only difference is that there's a new test
in the test suite.) It will be checked in to CVS by the end of
the day.
-Mark
--
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: mcc@xxxxxxxxxxxxxx ------- Personal Email: markcc@xxxxxxxxxxx