Re: Missing release on reporter.a.o

Hello Ralph, 2015-05-12 8:05 GMT+02:00 Ralph Goers : > I did it myself. > sorry, I'm still a bit lost. How can you do that? I'm looking at the https://reporter.apache.org/ page and it only shows me the report with no possibility to add JIRA projects and/or prefixes. Thanks! Benedikt > > Ralph

Re: Missing release on reporter.a.o

I did it myself. Ralph > On May 11, 2015, at 10:54 PM, Benedikt Ritter wrote: > > Hello Ralph, > > 2015-05-12 7:34 GMT+02:00 Ralph Goers >: > >> It would seem that for each commons subproject you need to add the Jira >> project and specify a prefix (such as

Re: Missing release on reporter.a.o

Hello Ralph, 2015-05-12 7:34 GMT+02:00 Ralph Goers : > It would seem that for each commons subproject you need to add the Jira > project and specify a prefix (such as LANG, VFS) etc, so that you can > associate the release numbers with the project name. Of course, I expect > you actually have to

Re: Missing release on reporter.a.o

It would seem that for each commons subproject you need to add the Jira project and specify a prefix (such as LANG, VFS) etc, so that you can associate the release numbers with the project name. Of course, I expect you actually have to have recorded the releases in Jira. Ralph > On May 11, 201

Re: Missing release on reporter.a.o

I do not know much about it but Ralph Goers just fixed Log4j for us in this dept. You may want to ask him (on the log4j dev ML?) Gary On Sun, May 10, 2015 at 10:55 PM, Benedikt Ritter wrote: > If you're talking about [lang] 3.4, then I'm the one to blame :-) I had > problems using the reporter

Re: [DISCUSS] Release imaging in its current state? (or release it never...)

On Mon, May 11, 2015 at 5:06 PM, Phil Steitz wrote: > On 5/11/15 11:27 AM, Benedikt Ritter wrote: > > Hi, > > > > over the past few month I've been working on [imaging]. Looking through > the > > list of FindBugs and Checkstyle issues, I wonder what we should do with > > imaging. The code doesn't

Re: [DISCUSS] Release imaging in its current state? (or release it never...)

On 5/11/15 11:27 AM, Benedikt Ritter wrote: > Hi, > > over the past few month I've been working on [imaging]. Looking through the > list of FindBugs and Checkstyle issues, I wonder what we should do with > imaging. The code doesn't meet our quality requirements, yet people seem to > be using imagin

Re: [DISCUSS] Release imaging in its current state? (or release it never...)

I think we should release it indeed but as what is the question: an alpha, beta or 1.0. I'm not fully able to dig in though, I am OOT on a biz trip and recovering from a cold to boot. Would you mind digging through the email archives? I _know_ we've discussed this in the past and there is a propos

[DISCUSS] Release imaging in its current state? (or release it never...)

Hi, over the past few month I've been working on [imaging]. Looking through the list of FindBugs and Checkstyle issues, I wonder what we should do with imaging. The code doesn't meet our quality requirements, yet people seem to be using imaging. I wonder if we should simply release [imaging] in i

Re: [lang] Check for Duplicate Event Listener

Hello Matthew, 2015-05-11 18:01 GMT+02:00 Matthew Aguirre : > I would like to add support to check for a duplicate event listener to the > org.apache.commons.lang3.event.EventListenerSupport class. > This would save me (and possibly others) from then checking the listeners > before adding. > >

Re: [lang] Check for Duplicate Event Listener

On Mon, May 11, 2015 at 12:43 PM James Carman wrote: > > Great ideas! I would think the non-duplicate part would be a global thing > for that particular EventListenerSupport object, so it should probably be > part of the constructor. That would change the serialization of the > objects, which i

Re: [lang] Check for Duplicate Event Listener

On Mon, May 11, 2015 at 12:02 PM Matthew Aguirre wrote: > I would like to add support to check for a duplicate event listener to the > org.apache.commons.lang3.event.EventListenerSupport class. > This would save me (and possibly others) from then checking the listeners > before adding. > >1.

[lang] Check for Duplicate Event Listener

I would like to add support to check for a duplicate event listener to the org.apache.commons.lang3.event.EventListenerSupport class. This would save me (and possibly others) from then checking the listeners before adding. 1. Should I just submit a ticket or should I implement a change within

[GitHub] commons-cli pull request: there is no class DefaultParser in the j...

Github user asfgit closed the pull request at: https://github.com/apache/commons-cli/pull/1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is e

Re: [PROPOSAL][Git] Tidy up SVN repos for components using Git

Le 2015-05-11 08:57, Jörg Schaible a écrit : +1 +1 Luc sebb wrote: Following on from the discussion, here is what I propose. ***The intention is to ensure that the SVN repo is not used by accident, but still allow users to find the Git repo if they only have the SVN URL.*** [Note: as pa