commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Sitze <rsi...@us.ibm.com>
Subject Re: [logging] Enterprise Common Logging... dare we say 2.0?
Date Tue, 21 Dec 2004 18:08:14 GMT
Regarding coding, I do have someone here who is champing at the bit to 
start submitting code to me, for checkin.  Not to say others cannot, just 
that before you put any of your own time into this, know that there are 
other resources being made available.

I do think we can start teasing some elements of this apart, and dropping 
prototype code in the near future.  If nothing else, it would be good to 
have something to poke at.  When we do get to that point, would suggest a 
seperate directory in the CVS repository.

Finally, regarding version numbers.  I'm willing to not make that call 
yet, see where we end up, and call it what it is in the end.

<ras>

*******************************************
Richard A. Sitze
IBM WebSphere WebServices Development

robert burrell donkin <robertburrelldonkin@blueyonder.co.uk> wrote on 
12/20/2004 04:13:56 PM:

> On 18 Dec 2004, at 20:52, Curt Arnold wrote:
> > On Dec 18, 2004, at 12:24 PM, Richard Sitze wrote:
> 
> <snip>
> 
> >> We ARE assuming that maintaining SOME SIGNIFICANT compatibility with 
> >> the
> >> existing JCL is of paramount importance.  We are NOT trying to 
> >> standardize
> >> on some "other" API within the industry, but rather to evolve an 
> >> existing
> >> standard with new function.  The API's are based *functionally* on 
> >> JSR-47
> >> and other logging implementations.  It's fair to say that there is 
> >> more
> >> than a little experience being brought to bear on this effort within 
> >> the
> >> Jakarta community.
> >>
> >
> > Again, I'm coming into this late.   Is there a requirements doc of 
> > some sort other than what was in this thread, have there been any 
> > votes, anything in CVS, any timeline?
> 
> there was a vote but i think it was a little premature. certainly, 
> there's been no pressure to conclude it and it seems to me that the 
> present consensus is that more talk and thought is needed.
> 
> commons appears to be in the process of migrating to subversion. i feel 
> an urge to code but it'd be better to take a branch or three to further 
> the discussion in code. so for the moment, i don't think we'll see any 
> commits for a while yet. certainly, i wouldn't feel comfortable with 
> any as yet.
> 
> personally speaking, i think that refactoring the discovery process is 
> a pre-requisite to firming up the design. i have seen too much 
> discussion on that yet so maybe we're still a little way off...
> 
> - robert
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message