[continuum] BUILD FAILURE: Commons Codec

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=46424&projectId=159 Build statistics: State: Failed Previous State: Failed Started at: Mon 4 Feb 2008 22:30:41 -0800 Finished at: Mon 4 Feb 2008 22:31:23 -0800 Total time: 41s Build Trigger: Schedule Build Numb

[continuum] BUILD FAILURE: Commons Codec

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=46424&projectId=159 Build statistics: State: Failed Previous State: Failed Started at: Mon 4 Feb 2008 22:30:41 -0800 Finished at: Mon 4 Feb 2008 22:31:23 -0800 Total time: 41s Build Trigger: Schedule Build Numb

Re: [io] 2.0 Moving to minimum of JDK 1.5

On Feb 4, 2008 8:47 PM, Niall Pemberton <[EMAIL PROTECTED]> wrote: > We've discussed moving to a minimum of JDK 1.5 for IO 2.0 previously - > theres also an JIRA report here: >http://issues.apache.org/jira/browse/IO-140 > > From memory the preference was to move to a new package name - how > a

[io] 2.0 Moving to minimum of JDK 1.5

We've discussed moving to a minimum of JDK 1.5 for IO 2.0 previously - theres also an JIRA report here: http://issues.apache.org/jira/browse/IO-140 >From memory the preference was to move to a new package name - how about "org.apache.commons.io2"? Are there any objections to me creating an IO

[all] Commons Build Plugin

The ant plugin I've been playing with in the Sandbox provides a way to generate custom JIRA issue tracking pages and download pages for components: http://commons.apache.org/sandbox/commons-build-plugin/ If we add it to the commons-parent, then each component just need a few properties configurin

Re: Commons Net 1.4.x Service Release?

Hi Martin Sorry for the late reply. It's been a busy year for me, and I am having trouble allocating sufficient time to [net] at the moment to close off the remaining issues and schedule a release, hence the delay. There seem to be a trickle of bug reports, but unfortunately not much manpower

[continuum] BUILD FAILURE: Commons Codec

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=46253&projectId=159 Build statistics: State: Failed Previous State: Error Started at: Mon 4 Feb 2008 13:13:23 -0800 Finished at: Mon 4 Feb 2008 13:13:50 -0800 Total time: 26s Build Trigger: Schedule Build Numbe

[continuum] BUILD FAILURE: Commons Codec

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=46253&projectId=159 Build statistics: State: Failed Previous State: Error Started at: Mon 4 Feb 2008 13:13:23 -0800 Finished at: Mon 4 Feb 2008 13:13:50 -0800 Total time: 26s Build Trigger: Schedule Build Numbe

Re: svn commit: r617341 - in /commons/sandbox/commons-build-plugin/src/main: resources/commons-xdoc-templates/ scripts/

On Feb 4, 2008 6:28 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > Niall Pemberton wrote: > > On Feb 2, 2008 4:56 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > >> Would it be possible to remove the property "commons.release.version" > >> and just use "project.version" instead, in the download-

Re: svn commit: r617341 - in /commons/sandbox/commons-build-plugin/src/main: resources/commons-xdoc-templates/ scripts/

Niall Pemberton wrote: On Feb 2, 2008 4:56 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: Would it be possible to remove the property "commons.release.version" and just use "project.version" instead, in the download-page-template? I don't think so, since most of the time that will be set to -S

[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