RE: [VOTE] Release commons-parent 5

Dennis Lundberg wrote: > Hi, > > It's time to release commons-parent again. The changes since the last > release in summary: > > - Activate ciManagement section > - Add commits and issues mailing-lists > - Use maven-remote-resources-plugin to handle license and notice files > - Add a ci profile

Re: [VOTE] Release commons-parent 5

+1 nonbinding. On Nov 11, 2007 6:37 PM, Phil Steitz <[EMAIL PROTECTED]> wrote: > +1 > > Thanks! > > Phil > > On Nov 11, 2007 2:43 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > It's time to release commons-parent again. The changes since the last > > release in summary: > > > > -

Re: [VOTE] Release commons-parent 5

+1 Thanks! Phil On Nov 11, 2007 2:43 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > Hi, > > It's time to release commons-parent again. The changes since the last > release in summary: > > - Activate ciManagement section > - Add commits and issues mailing-lists > - Use maven-remote-resources-pl

Re: [VOTE] Release commons-parent 5

+1 Niall On Nov 11, 2007 9:43 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > Hi, > > It's time to release commons-parent again. The changes since the last > release in summary: > > - Activate ciManagement section > - Add commits and issues mailing-lists > - Use maven-remote-resources-plugin to

Re: [VOTE] Release commons-parent 5

+1 On 11/11/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > Hi, > > It's time to release commons-parent again. The changes since the last > release in summary: > > - Activate ciManagement section > - Add commits and issues mailing-lists > - Use maven-remote-resources-plugin to handle license and

Re: [VOTE] Release commons-parent 5

On Nov 11, 2007 10:43 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > [ ] +1 > [ ] =0 > [ ] -1 +1 -- Look, that's why there's rules, understand? So that you think before you break 'em. -- (Terry Pratchett, Thief of Time) ---

Edit: Re: svn commit: r593964 - in /commons/proper/collections/branches/collections_jdk5_branch/src: java/org/apache/commons/collections/CollectionUtils.java test/org/apache/commons/collections/TestCo

Good patch - seems I need to update my compiler warnings a bit. Nice to get to 100% - one thing that interested me about that was testing the extension of CollectionUtils. People - please see https://issues.apache.org/jira/browse/COLLECTIONS-276. And while CollectionUtils is updated for generic

Re: svn commit: r593964 - in /commons/proper/collections/branches/collections_jdk5_branch/src: java/org/apache/commons/collections/CollectionUtils.java test/org/apache/commons/collections/TestCollecti

Good patch - seems I need to update my compiler warnings a bit. Nice to get to 100% - one thing that interested me about that was testing the extension of CollectionUtils. People - *please see https://issues.apache.org/jira/browse/COLLECTIONS-276*. And while CollectionUtils is updated for ge

[VOTE] Release commons-parent 5

Hi, It's time to release commons-parent again. The changes since the last release in summary: - Activate ciManagement section - Add commits and issues mailing-lists - Use maven-remote-resources-plugin to handle license and notice files - Add a ci profile that Continuum can use - Add required A

[DRAFT] Apache Commons Board Report, November 2007

Corrections? Additions? cheers -- Torsten Apache Commons Board Report, November 2007 Summary === o Question has come up whether commons codec is thread safe - needs better documentation o More activity on commons jexl - roadmap towards 2.0 o Discussion about moving fam (

[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

Re: [VOTE] Release Commons Configuration 1.5 based on RC2

Sorry -1 from me to release this. The source distro is (slightly) different from what was tagged as "CONFIGURATION_1_5RC2". IMO the release candidate should be built on a clean checkout of whats been tagged in svn. project.xml has had the jdiff report removed project.properties has had the "maven.