Re: svn commit: r1754208 - in /commons/proper/dbcp/tags/DBCP_2_2_RC1: ./ doc/ src/

I used the correct tag in the pom for rc2, but that's been put on hold anyways. On 18 August 2016 at 16:35, Gary Gregory wrote: > On Aug 18, 2016 2:29 PM, "sebb" wrote: > > > > On 29 July 2016 at 01:25, Matt Sicker wrote: > > > Would

Re: svn commit: r1754208 - in /commons/proper/dbcp/tags/DBCP_2_2_RC1: ./ doc/ src/

On Aug 18, 2016 2:29 PM, "sebb" wrote: > > On 29 July 2016 at 01:25, Matt Sicker wrote: > > Would it be ok to just manually update the pom after doing an svn cp? > > No, please don't change tags. > They are supposed to be immutable, and must match what was

RM karma (was: [DBCP] Release 2.2?)

On 27 July 2016 at 17:06, Gary Gregory wrote: > WRT the KEYS file, I'm not sure we can give karma without Matt being an > actual Commons Committer or a PMC member. Is there such a thing as a Commons Committer since we opened SVN/Git to all? I think karma is granted by

Re: svn commit: r1754208 - in /commons/proper/dbcp/tags/DBCP_2_2_RC1: ./ doc/ src/

On 29 July 2016 at 01:25, Matt Sicker wrote: > Would it be ok to just manually update the pom after doing an svn cp? No, please don't change tags. They are supposed to be immutable, and must match what was voted and released. > Subversion does allow updating tags. Otherwise, I

Re: [RESULT][VOTE] Release Configuration 2.1 based on RC3

A vote is normally at least 72 hours, but it can be shorter if announced in advanced, for a security fix for example. I do not see a problem with saying that the additional binding vote counts. You can send another vote result email. Gary On Aug 18, 2016 12:48 PM, "Oliver Heger"

Re: [RESULT][VOTE] Release Configuration 2.1 based on RC3

Am 16.08.2016 um 21:40 schrieb Oliver Heger: > The vote to release Configuration 2.1 based on RC3 failed with the > following binding votes: > > Gary Gregory: -1 > Jörg Schaible:+1 > Oliver Heger: +1 After closing the vote, two more votes have been cast: - Raviteja Lokineni: +1

Re: [DAEMON] Who is having a look at DAEMON?

On 18 August 2016 at 18:19, Benedikt Ritter wrote: > Thank you! > > Mark Thomas schrieb am Do., 18. Aug. 2016 um 19:06 Uhr: > >> On 18/08/2016 18:59, Mark Thomas wrote: >> > On 18/08/2016 17:36, sebb wrote: >> >> I have done some work on it in the past, and

Re: [DAEMON] Who is having a look at DAEMON?

Thank you! Mark Thomas schrieb am Do., 18. Aug. 2016 um 19:06 Uhr: > On 18/08/2016 18:59, Mark Thomas wrote: > > On 18/08/2016 17:36, sebb wrote: > >> I have done some work on it in the past, and even made some fixes to > >> the assembler code IIRC. > >> > >> The Java code is

Re: [DAEMON] Who is having a look at DAEMON?

On 18/08/2016 18:59, Mark Thomas wrote: > On 18/08/2016 17:36, sebb wrote: >> I have done some work on it in the past, and even made some fixes to >> the assembler code IIRC. >> >> The Java code is trivial. >> The assembler ('C') code is complicated in places and has limited >> documentation. >>

Re: [DAEMON] Who is having a look at DAEMON?

On 18/08/2016 17:36, sebb wrote: > I have done some work on it in the past, and even made some fixes to > the assembler code IIRC. > > The Java code is trivial. > The assembler ('C') code is complicated in places and has limited > documentation. > > However the main problem is the Windows

Re: [DAEMON] Who is having a look at DAEMON?

I have done some work on it in the past, and even made some fixes to the assembler code IIRC. The Java code is trivial. The assembler ('C') code is complicated in places and has limited documentation. However the main problem is the Windows build. It needs special handling to ensure it links

Re: [DAEMON] Who is having a look at DAEMON?

I've noticed some tickets go by as well. I have not taken the time to look into any of it :-( I won't be able to in the near future either. Gary On Thu, Aug 18, 2016 at 2:58 AM, Benedikt Ritter wrote: > Hello, > > is anybody actively having a look at the [daemon] component?

Re: [ALL] Configure Jenkins to report to notifications@ ?

To me, failed build messages are appropriate on the dev ML. Jenkins' setup just needs to be fixed. But I won't oppose the change, it will all ends up in my inbox anyway. Gary On Aug 18, 2016 7:35 AM, "Benedikt Ritter" wrote: > Hello, > > currently the Jenkins infrastructure

Re: [rng] JDK version (Was: ... commit ...)

Hi Gilles, Gilles schrieb am Do., 18. Aug. 2016 um 16:46 Uhr: > Hi. > > On Thu, 18 Aug 2016 14:33:30 +, Benedikt Ritter wrote: > > Hello, > > > > schrieb am Do., 18. Aug. 2016 um 16:32 Uhr: > > > >> Repository: commons-rng > >> Updated

Jenkins build is back to normal : commons-validator #7

See - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

[rng] JDK version (Was: ... commit ...)

Hi. On Thu, 18 Aug 2016 14:33:30 +, Benedikt Ritter wrote: Hello, schrieb am Do., 18. Aug. 2016 um 16:32 Uhr: Repository: commons-rng Updated Branches: refs/heads/master cccd43c05 -> 294fa53a2 Fix dependency info. Project:

[ALL] Configure Jenkins to report to notifications@ ?

Hello, currently the Jenkins infrastructure seems to be a bit unpredictable. Builds fail for no apparent reason because they are executed on different slaves. The notifications spam our dev list, so I was thinking about configuring all the jobs to report to notificati...@commons.apache.org.

Re: [1/3] commons-rng git commit: Fix dependency info.

Hello, schrieb am Do., 18. Aug. 2016 um 16:32 Uhr: > Repository: commons-rng > Updated Branches: > refs/heads/master cccd43c05 -> 294fa53a2 > > > Fix dependency info. > > > Project: http://git-wip-us.apache.org/repos/asf/commons-rng/repo > Commit:

Re: [VOTE] Release Configuration 2.1 based on RC3

Hello Oliver, Sorry that it took me so long. +1 for this release. The problems with Java 1.6 have been resolved. Good work! When building with Java 9 EA the build fails. I think we need to investigate this for all our components soon. Benedikt Oliver Heger

Re: Moving components to git - what to do with the SVN tree

On 31 July 2016 at 12:14, Benedikt Ritter wrote: > Hi, > > I've talked to infra and they have set up permission so that PMC members > can write to https://svn.apache.org/repos/asf/commons/_moved_to_git The > process of migrating a component to git is now as follows: > > -

Re: [IMAGING] issue tracker?

Hello Amedee, Amedee Van Gasse schrieb am Do., 18. Aug. 2016 um 15:30 Uhr: > Where can I find a single issue tracker with all issues that block a > release of commons-imaging? And, if available, estimated time / story > points / other metric for those blocking

Build failed in Jenkins: commons-validator #6

See Changes: [britter] VALIDATOR-401: IBANValidator fails for Seychelles and Ukraine. Thanks to Björn Raupach for reporting this issue. -- [...truncated 18 lines...] AU

Re: [VALIDATOR] Release 1.5.1 not marked as released in JIRA

sebb schrieb am Do., 18. Aug. 2016 um 15:38 Uhr: > Done. > Thank you! > > The release date was present, but the version had not been marked as > released. > It's easy to overlook that. > > On 18 August 2016 at 14:33, Benedikt Ritter wrote: > > Hi, > > >

Re: [VALIDATOR] Release 1.5.1 not marked as released in JIRA

Done. The release date was present, but the version had not been marked as released. It's easy to overlook that. On 18 August 2016 at 14:33, Benedikt Ritter wrote: > Hi, > > in trunk we have version 1.5.2-SNAPSHOT but in JIRA version 1.5.1 has not > been marked as released.

Re: Move Site from CMS to Git

On 18 August 2016 at 14:02, sebb wrote: > On 18 August 2016 at 13:49, Jochen Wiedmann wrote: >> On Thu, Aug 18, 2016 at 2:44 PM, sebb wrote: >>> Please note that CMS and Git are orthogonal. >>> >>> CMS can be used with either SVN or

[VALIDATOR] Release 1.5.1 not marked as released in JIRA

Hi, in trunk we have version 1.5.2-SNAPSHOT but in JIRA version 1.5.1 has not been marked as released. I think we should mark it as released. Benedikt

Re: Move Site from CMS to Git

On 18 August 2016 at 14:22, Jochen Wiedmann wrote: > On Thu, Aug 18, 2016 at 3:02 PM, sebb wrote: > >> Buildbot is also used with svnpubsub. > > Just guessing: The problem might be, that SVN doesn't allow a > technical user performing a Commit. At

Re: [IMAGING] issue tracker?

Where can I find a single issue tracker with all issues that block a release of commons-imaging? And, if available, estimated time / story points / other metric for those blocking issues? Based on that input, we at iText Software can decide how we can work with Apache Commons to get to a

Re: Move Site from CMS to Git

On Thu, Aug 18, 2016 at 3:02 PM, sebb wrote: > Buildbot is also used with svnpubsub. Just guessing: The problem might be, that SVN doesn't allow a technical user performing a Commit. At least, this has been a problem in the past. Jochen -- The next time you hear: "Don't

Re: Move Site from CMS to Git

On 18 August 2016 at 13:49, Jochen Wiedmann wrote: > On Thu, Aug 18, 2016 at 2:44 PM, sebb wrote: >> Please note that CMS and Git are orthogonal. >> >> CMS can be used with either SVN or Git (strictly speaking >> svnpubsub/gitpubsub) > > That may be

Re: Move Site from CMS to Git

On Thu, Aug 18, 2016 at 2:44 PM, sebb wrote: > Please note that CMS and Git are orthogonal. > > CMS can be used with either SVN or Git (strictly speaking svnpubsub/gitpubsub) That may be true. However, it doesn't really match with the discussions that I had with Infra. (Which

Re: [rng] New "checkstyle" config is checking "src/test"

On Thu, Aug 18, 2016 at 3:48 PM, sebb wrote: > > will never take the configuration for the checkstyle report into account. > > Maven behaviour calling goals directly ... > > For this reason some POMs include both report and build entries for > tools such as RAT, Checkstyle,

Re: [rng] New "checkstyle" config is checking "src/test"

On 18 August 2016 at 07:37, Jörg Schaible wrote: > Hi Gilles, > > Gilles wrote: > >> On Thu, 18 Aug 2016 02:12:21 +0300, Artem Barger wrote: >>> On Thu, Aug 18, 2016 at 1:45 AM, Gilles >>> >>> wrote: >>> It's something

Re: Move Site from CMS to Git

Hello Jochen, Jochen Wiedmann schrieb am Do., 18. Aug. 2016 um 14:19 Uhr: > On Thu, Aug 18, 2016 at 1:23 PM, Benedikt Ritter > wrote: > > > If it's possible we should investigate whether it makes stuff easier for > us. > > The reason why I am

Re: Move Site from CMS to Git

Please note that CMS and Git are orthogonal. CMS can be used with either SVN or Git (strictly speaking svnpubsub/gitpubsub) On 18 August 2016 at 13:19, Jochen Wiedmann wrote: > On Thu, Aug 18, 2016 at 1:23 PM, Benedikt Ritter wrote: > >> If it's

Re: [Website] download link could not redirect consistently

The CMS workspace has now been sorted by infra, and the link is now working. == The problem was that the SVN entry here: https://svn.apache.org/repos/infra/websites/staging/commons/trunk/content/crypto and the actual website, which is derived from the staging area above

Re: Move Site from CMS to Git

On Thu, Aug 18, 2016 at 1:23 PM, Benedikt Ritter wrote: > If it's possible we should investigate whether it makes stuff easier for us. The reason why I am driving this: The CMS makes me sick. Whatever I intend to do on the site, it is in the way. That is the main reason, why

Re: Move Site from CMS to Git

Jochen Wiedmann schrieb am Do., 18. Aug. 2016 um 13:14 Uhr: > On Thu, Aug 18, 2016 at 12:28 PM, Benedikt Ritter > wrote: > > > I always thought our SVN/CMS workflow is mandatory. Do you know projects > > who use git for site publication already? >

Re: Move Site from CMS to Git

On Thu, Aug 18, 2016 at 12:28 PM, Benedikt Ritter wrote: > I always thought our SVN/CMS workflow is mandatory. Do you know projects > who use git for site publication already? According to Infra, it isn't mandatory. See https://issues.apache.org/jira/browse/INFRA-12228.

Re: [Website] download link could not redirect consistently

sebb schrieb am Mi., 17. Aug. 2016 um 19:19 Uhr: > On 17 August 2016 at 17:07, sebb wrote: > > On 17 August 2016 at 16:38, sebb wrote: > >> On 5 August 2016 at 10:34, Sun, Dapeng wrote: > >>> Hello > >>> > >>> The

Re: Move Site from CMS to Git

Hi Jochen, Jochen Wiedmann schrieb am Do., 18. Aug. 2016 um 09:03 Uhr: > Hi, > > I'd like to have our site moved away from the CMS to Git. Because, if > we have done that, we can also have a set of buildjobs created, that > watch on commits, rebuild the site, and

Re: [rng] Update .gitignore to ignore MacOS related files.

Hi Jochen, Jochen Wiedmann schrieb am Do., 18. Aug. 2016 um 09:06 Uhr: > On Tue, Aug 16, 2016 at 9:10 PM, Benedikt Ritter > wrote: > > > I personally think this kind of ignores belong into your global > .gitignore > > file. But that's just me :-)

[DAEMON] Who is having a look at DAEMON?

Hello, is anybody actively having a look at the [daemon] component? I noticed several requests on the user ML and some issues in JIRA lately but I don't have the feeling someone is responding. Benedikt

Re: [LANG] LANG-1252 - NumberUtils.isNumber and NumberUtils.createNumber resolve inconsistently

On Tue, Aug 16, 2016 at 9:10 PM, Benedikt Ritter wrote: >> > On Jul 31, 2016, at 3:03 PM, Rob Tompkins wrote: >> > System.out.println(NumberUtils.isParsable("+2")); > false >> > System.out.println(NumberUtils.createNumber("+2")); ---> 2 >> If I had

Re: [rng] Update .gitignore to ignore MacOS related files.

On Tue, Aug 16, 2016 at 9:10 PM, Benedikt Ritter wrote: > I personally think this kind of ignores belong into your global .gitignore > file. But that's just me :-) AFAIK, it doesn't hurt, if they are present in both, does it? Jochen -- The next time you hear: "Don't

Re: [VOTE][LAZY] Migrate Apache Commons DBCP to Git

+1 On Wed, Aug 17, 2016 at 4:57 AM, Gary Gregory wrote: > +1 > > Gary > > On Tue, Aug 16, 2016 at 7:00 PM, Matt Sicker wrote: > >> I'd like to call a VOTE by LAZY consensus to migrate dbcp to git. The 2.2 >> release process is currently on hold, so I'd

Move Site from CMS to Git

Hi, I'd like to have our site moved away from the CMS to Git. Because, if we have done that, we can also have a set of buildjobs created, that watch on commits, rebuild the site, and commit the updated site. Right now, I view the site as a nightmare. WDYT? Jochen -- The next time you hear:

Re: [rng] New "checkstyle" config is checking "src/test"

Hi Gilles, Gilles wrote: > On Thu, 18 Aug 2016 02:12:21 +0300, Artem Barger wrote: >> On Thu, Aug 18, 2016 at 1:45 AM, Gilles >> >> wrote: >> >>> >>> It's something related to the plain >>> checkstyle:checkstyle >>> target. >> >> >> ​Added a rule to skip these