commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: [human-assisted gump] log4j back incompatible change
Date Fri, 29 Oct 2004 12:13:11 GMT

Hi,
This seems already covered, but I'd like to offer my help as well in resolving these (while
keeping Ceki's change intact), as needed.

Yoav Shapira http://www.yoavshapira.com
 

>-----Original Message-----
>From: Ceki Gülcü [mailto:ceki@qos.ch]
>Sent: Friday, October 29, 2004 7:07 AM
>To: craigmcc@apache.org; Jakarta Commons Developers List
>Cc: Gump; log4j-dev@logging.apache.org; velocity-dev@jakarta.apache.org;
>dev@ant.apache.org; stefano@apache.org
>Subject: Re: [human-assisted gump] log4j back incompatible change
>
>Hi Craig,
>
>Apparently, since you removed the Log4JCategoryLog class, commons-logging
>builds fine today. Do you have a copy of yesterday's errors for
>commons-logging? If you do, could I please have a look at them?
>
>Thanks in advance,
>
>At 07:40 AM 10/29/2004, Craig McClanahan wrote:
>>I can help out with over half of the gump failures.  Commons Logging
>>deprecated Log4JCategoryLog a long time ago, when Log4J deprecated
>>Category in favor of Logger.
>>
>>C-L itself hasn't used Log4JCategoryLog for several releases, so this
>>change will be transparent to the vast majority of Commons Logging
>>users.
>>
>>Craig McClanahan
>>
>>
>>
>>On Fri, 29 Oct 2004 01:07:38 -0400, Stefano Mazzocchi
>><stefano@apache.org> wrote:
>> > Ceki,
>> >
>> > your action
>> >
>> >
>> http://cvs.apache.org/viewcvs.cgi/logging-
>log4j/src/java/org/apache/log4j/Category.java?r1=1.88&r2=1.89&diff_format=h
>> >
>> > caused a compilation failure of the following projects:
>> >
>> >    - commons-logging
>> >    - velocity
>> >    - ant
>> >
>> > and, as a result, caused a drop in the gump's success from 83% to 53%,
>> > for more info see:
>> >
>> >   http://brutus.apache.org/gump/public/project_todos.html
>> >
>> > Now, since this is a back incompatible change, we (the gumpmeisters)
>> > would like to know:
>> >
>> >   1) if you might be willing to revert the change if you did not intend
>> > to cause such effect
>> >
>> >   2) if not, if you are willing to move the previous version of the
>tree
>> > into a branch so that we can migrate the dependencies to that
>> >
>> >   3) if not, if you are willing to work with the offended dependees to
>> > restore their success status.
>> >
>> >   4) if not, if you have any alternative suggestion on how to move
>forward.
>> >
>> > please understand that we have no preference in which road the log4j
>> > project decides to go, we are only interested in giving a chance to
>> > those 322 projects that were affected by this to keep having build
>> > information.
>> >
>> > Thank you very much in advance for your cooperation.
>> >
>> > --
>> > Stefano, doing by hand what gump should be able to do in the future.
>> >
>> >
>> >
>
>--
>Ceki Gülcü
>
>      For log4j documentation consider "The complete log4j manual"
>      http://www.qos.ch/shop/products/eclm/
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org




This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.


---------------------------------------------------------------------
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