Re: Picking up the ball from Niclas (ugh!) on Velocity

2004-12-01 Thread Ceki Gülcü
On 2004-11-30 11:19:33, Eric Pugh wrote: Now, partly that may be a communication thing.. If Log4j fails, they get emailed. If log4j breaks every body else, they don't... Without active involvement by a group, the prospect of keeping things working becomes a thankless task (witness Niclas's

RE: Picking up the ball from Niclas (ugh!) on Velocity

2004-11-30 Thread Eric Pugh
: Niclas Hedhman [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 30, 2004 6:36 AM To: Gump code and data Subject: Re: Picking up the ball from Niclas (ugh!) on Velocity On Tuesday 30 November 2004 07:45, Stefano Mazzocchi wrote: Gump is about establishing communication channels between

Re: Picking up the ball from Niclas (ugh!) on Velocity

2004-11-30 Thread Geir Magnusson Jr
On Nov 30, 2004, at 6:19 AM, Eric Pugh wrote: I think what he means is that we can't expect people to make changes just to make Gump happy. But, we can *attempt* to influence them to help. And I think that is where we are going wrong. For instance, Fulcrum components didn't build very well

Re: Picking up the ball from Niclas (ugh!) on Velocity

2004-11-30 Thread Niclas Hedhman
On Tuesday 30 November 2004 20:18, Geir Magnusson Jr wrote: On Nov 30, 2004, at 6:19 AM, Eric Pugh wrote: Geir's email highlights a very clear issue with the whole deprecation/version cycle. He can't switch to log4j until it releases. They don't want to keep deprecated code around for

Re: Picking up the ball from Niclas (ugh!) on Velocity

2004-11-30 Thread Geir Magnusson Jr
On Nov 30, 2004, at 8:18 AM, Niclas Hedhman wrote: On Tuesday 30 November 2004 20:18, Geir Magnusson Jr wrote: On Nov 30, 2004, at 6:19 AM, Eric Pugh wrote: Geir's email highlights a very clear issue with the whole deprecation/version cycle. He can't switch to log4j until it releases. They don't

Re: Picking up the ball from Niclas (ugh!) on Velocity

2004-11-30 Thread Stefano Mazzocchi
Niclas Hedhman wrote: The rule should be to start fixing gump and fix the communication channels rather than fixing the metadata to route around the problems. Cool, but then you told me Don't change people we should work around them [projects not willing to co-operate]... I would call that

Picking up the ball from Niclas (ugh!) on Velocity

2004-11-29 Thread Eric Pugh
So, I thought I would just submit a patch to Velocity to fix the velocity/log4j problem and everything would be fine. Wrong.. The issue is the non backwards compatible API change to log4j. And, I saw Niclas email about it as well. So, I dug some more and according to this email: http:[EMAIL

Re: Picking up the ball from Niclas (ugh!) on Velocity

2004-11-29 Thread Stefano Mazzocchi
Eric Pugh wrote: So, I thought I would just submit a patch to Velocity to fix the velocity/log4j problem and everything would be fine. Wrong.. The issue is the non backwards compatible API change to log4j. And, I saw Niclas email about it as well. So, I dug some more and according to this

RE: Picking up the ball from Niclas (ugh!) on Velocity

2004-11-29 Thread Stephen McConnell
-Original Message- From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED] Gump is about establishing communication channels between development communities. ROTFLOL - To unsubscribe, e-mail: [EMAIL PROTECTED] For

Re: Picking up the ball from Niclas (ugh!) on Velocity

2004-11-29 Thread Niclas Hedhman
On Tuesday 30 November 2004 07:45, Stefano Mazzocchi wrote: Gump is about establishing communication channels between development communities. On the other hand, if you are interested in creating a social engineering support tool and you are willing to get your hands dirty in python and