[codec] any takers for CODEC-75 patch?

Hi, I created CODEC-75 (url-safe Base64) and attached a 20KB patch to the ticket. Anyone interested in committing this? The patch improves codec's base64 handling in two ways: 1. Ability to decode base64 streams which are missing the final padding characters. 2. Introduces "Base64.encodeBase6

Re: [all] Incorrect release info in the doap files

On Wed, May 27, 2009 at 5:57 AM, Emmanuel Bourg wrote: > Could everyone look at their projects and fix the files please? Just as a note - there's no reason why someone can't do all of them if they want. Should be a simple regex. Hen

Re: [all] Incorrect release info in the doap files

On 27/05/2009, Dennis Lundberg wrote: > Emmanuel Bourg wrote: > > I noticed that most of the Commons components listed on > > projects.apache.org have an empty release history. This is due to an > > incorrect syntax in the doap files. The releases are defined with: > > > > > > commons

Re: [all] Incorrect release info in the doap files

Emmanuel Bourg wrote: > I noticed that most of the Commons components listed on > projects.apache.org have an empty release history. This is due to an > incorrect syntax in the doap files. The releases are defined with: > > > commons-codec > 2004-07-10 > 1.3 > > > but it should

Re: Is JEXL an active project ?

On Wed, May 27, 2009 at 9:19 AM, Henrib wrote: > > Looking at the number of issues, commits & messages, it looks like JEXL does > not have a very voicefull community; are there still some committers around > or is the project in a semi-abandoned state? > If so, I suppose it would be OK to "fork" a

Re: [all] Source jars for released components

On Tue, May 26, 2009 at 10:42 PM, Phil Steitz wrote: > POOL-141 is asking for source jars for old versions of [pool] to be pushed > to maven central.  I think we talked about this before in relation to > another component, but I can't find the thread and can't recall the > resolution. > > Have we

Re: [cli] Git mirror available

Hi, On Wed, May 27, 2009 at 4:34 PM, Russel Winder wrote: > Is it guaranteed that the Git read-only mirror repository will always be > exactly up to date to the Subversion repository? (i.e. will every commit > to the Subversion store cause a refresh of the Git read-only mirror?) Yes. The mirror

Re: Is JEXL an active project ?

Hi , > Looking at the number of issues, commits & messages, it looks like JEXL does > not have a very voicefull community; are there still some committers around > or is the project in a semi-abandoned state? all Commons Committers can (theoretically) apply patches. But it cannot be too bad to br

Re: [cli] Git mirror available

Russel Winder a écrit : I just cloned the read-only repository -- took a few seconds, and works well. A lot better than doing a "git svn clone . . . " myself -- which takes a couple of days or so! Great! Regarding the inner working of the svn->git replication, the best is to ask the infrastr

Re: [cli] Git mirror available

Russel Winder wrote: > On Wed, 2009-05-27 at 11:30 +0100, Mark Thomas wrote: >> Paul Libbrecht wrote: >>> So commits in svn and in git are "compatible" ? >> http://www.apache.org/dev/git.html >> >> Mark > > Is it guaranteed that the Git read-only mirror repository will always be > exactly up to da

Re: [cli] Git mirror available

Emmanuel, On Wed, 2009-05-27 at 12:45 +0200, Emmanuel Bourg wrote: > Paul Libbrecht a écrit : > > So commits in svn and in git are "compatible" ? > > You can't commit to Git, the mirror is read-only. SVN commits are > automatically pushed to the Git mirror. > > It's just a convenience for extern

Re: [cli] Git mirror available

On Wed, 2009-05-27 at 11:30 +0100, Mark Thomas wrote: > Paul Libbrecht wrote: > > So commits in svn and in git are "compatible" ? > > http://www.apache.org/dev/git.html > > Mark Is it guaranteed that the Git read-only mirror repository will always be exactly up to date to the Subversion reposito

[math] Re: [all] Incorrect release info in the doap files

DOAP for [math] has been updated. Emmanuel Bourg wrote: I noticed that most of the Commons components listed on projects.apache.org have an empty release history. This is due to an incorrect syntax in the doap files. The releases are defined with: commons-codec 2004-07-10 1.3

[g...@vmgump]: Project commons-jelly-tags-fmt-test (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 gene...@gump.apache.org. Project commons-jelly-tags-fmt-test has an issue affecting its community integrat

Is JEXL an active project ?

Looking at the number of issues, commits & messages, it looks like JEXL does not have a very voicefull community; are there still some committers around or is the project in a semi-abandoned state? If so, I suppose it would be OK to "fork" a JEXL2 project (probably as a Google project ) so some fe

[all] Incorrect release info in the doap files

I noticed that most of the Commons components listed on projects.apache.org have an empty release history. This is due to an incorrect syntax in the doap files. The releases are defined with: commons-codec 2004-07-10 1.3 but it should be: commons-codec 2004-07-10

[g...@vmgump]: Project commons-configuration-test (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 gene...@gump.apache.org. Project commons-configuration-test has an issue affecting its community integrati

Re: [cli] Git mirror available

Paul Libbrecht a écrit : So commits in svn and in git are "compatible" ? You can't commit to Git, the mirror is read-only. SVN commits are automatically pushed to the Git mirror. It's just a convenience for external developers wishing to work on the code. Emmanuel Bourg

Re: [cli] Git mirror available

Paul Libbrecht wrote: > So commits in svn and in git are "compatible" ? http://www.apache.org/dev/git.html Mark > > paul > > > Le 27-mai-09 à 12:25, Emmanuel Bourg a écrit : > >> Thanks to the infrastructure team a Git mirror is now available for >> Commons CLI: >> >> git://git.apache.org/co

Re: [cli] Git mirror available

So commits in svn and in git are "compatible" ? paul Le 27-mai-09 à 12:25, Emmanuel Bourg a écrit : Thanks to the infrastructure team a Git mirror is now available for Commons CLI: git://git.apache.org/commons-cli.git Emmanuel Bourg ---

[cli] Git mirror available

Thanks to the infrastructure team a Git mirror is now available for Commons CLI: git://git.apache.org/commons-cli.git Emmanuel Bourg - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: