[EMAIL PROTECTED]: Project commons-net (in module apache-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-net has an issue affecting its community integration. This issue affects

Re: [all] Deleting STATUS.html files

+1 (The old charter [1] does reference a requirement for a status file, but this now appears to clearly be an 'old' charter since we became Apache Commons) SJC [1] http://commons.apache.org/oldcharter.html Henri Yandell wrote: Any +1s to delete the STATUS.html files? Many are out of date a

[EMAIL PROTECTED]: Project commons-jelly-tags-jaxme (in module commons-jelly) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-jelly-tags-jaxme has an issue affecting its community integration. This

[EMAIL PROTECTED]: Project commons-net (in module apache-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project commons-net has an issue affecting its community integration. This issue affects

Re: Support for OSGi

On Monday 31 December 2007 14:57, Alan D. Cabrera wrote: > I'm sorry but I'm not completely following.  What problems does this   > create?  How is it counter-productive. Commons-logging is not designed for a) OSGi environment with classes loaded and unloaded in runtime. b) Unifying Commons-logg