i didnt say i did!
3 maal Hoera voor pchapman!!!

i will commit it.

johan


On 4/26/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:

+1 because Philip did all that work :)

Eelco

On 4/26/07, Philip A. Chapman <[EMAIL PROTECTED]> wrote:
>
>  Done:  https://issues.apache.org/jira/browse/WICKET-509
>
> On Thu, 2007-04-26 at 08:00 -0500, Philip A. Chapman wrote:
>
> I'll eat my words "quick and easy replacement" and get a patch together
> for you.
>
> On Thu, 2007-04-26 at 14:42 +0200, Johan Compagner wrote:
>
> who makes the patch!
> On 4/25/07, Philip A. Chapman <[EMAIL PROTECTED]> wrote:>> I also prefer
slf4j (non-binding, of course).  slf4j does not suffer> from the
classloading issues and, in my experience, is a quick and easy> replacement
for commons-logging.>> On Wed, 2007-04-25 at 21:42 +0200, Xavier Hanin
wrote:> > Personnaly I prefer slf4j, especially because it doesn't suffer
from> > classloading issues.> >> > My 2c.> >> > Xavier> >> > On 4/25/07,
Eelco Hillenius <[EMAIL PROTECTED]> wrote:> > > Don't care
personally.> > >> > > Eelco> > >> > > On 4/25/07, Martijn Dashorst <
[EMAIL PROTECTED]> wrote:> > > > Did this change fall of the
charts from the backport lists? Must we> > > > change the logging to
SF$#L@@#4j or can we live with> commons-logging?> > > >> > > > Martijn (who
hasn't been bitten with clogging, yet)> > > >> > > > --> > > > Learn Wicket
at ApacheCon Europe: http://apachecon.com> > > > Join the wicket community
at irc.freenode.net: ##wicket> > > > Wicket 1.2.6 contains a very
important fix. Download Wicket now!> > > > http://wicketframework.org> > >
>> > >> >> >> --> Philip A. Chapman>> Desktop and Web Application
Development:> Java, .NET, PostgreSQL, MySQL, MSSQL> Linux, Windows 2000,
Windows XP>>
>
>   --
> Philip A. Chapman
>
> Desktop and Web Application Development:
> Java, .NET, PostgreSQL, MySQL, MSSQL
> Linux, Windows 2000, Windows XP
>
>     --
> Philip A. Chapman
>
> Desktop and Web Application Development:
> Java, .NET, PostgreSQL, MySQL, MSSQL
> Linux, Windows 2000, Windows XP
>
>
>

Reply via email to