Re: [DBCP] Working on 2.2 RC1

Matt, I've added you as a Commons committer. Gary On Wed, Jul 27, 2016 at 7:58 PM, Gary Gregory wrote: > Matt, > > Are you getting an error like >

Re: [DBCP] Working on 2.2 RC1

Matt, Are you getting an error like https://mail-archives.apache.org/mod_mbox/commons-dev/201509.mbox/%3ccajzrqky3hspuwg_9uk2tkjkj0j4wgkab5zugxvq8ymd3b+q...@mail.gmail.com%3E ? Gary On Wed, Jul 27, 2016 at 3:42 PM, Matt Sicker wrote: > Can I use sshfs/fuse, or does that not

RE: [VOTE] Release CRYPTO 1.0.0 based on RC1

Thank Benedikt for the detailed report. >>JceCipherTest.checkJceUnlimitedStrength:44 Testing requires support for an >>AES key length of 256, but the detected maximum key length is 128. This may >>indicate that the test environment is missing the JCE Unlimited Strength >>Jurisdiction Policy

Re: [DBCP] Working on 2.2 RC1

Can I use sshfs/fuse, or does that not work with home.apache.org? I can always try out Filezilla if necessary. I preferred the old method of just using scp. :/ Also, I still need Nexus permissions. That's my last blocker for now. On 27 July 2016 at 01:37, Benedikt Ritter

Re: [VOTE] Release Configuration 2.1 based on RC1

I ran 'mvn clean site'. Gary On Wed, Jul 27, 2016 at 12:30 PM, Oliver Heger wrote: > Thanks for the reviews so far. > > I tested with the Java 1.6 compatibility profile, and here a mvn clean > install is successful (using Maven 3.3.9). > > Any proposals which

Build failed in Jenkins: commons-cli #6

See Changes: [britter] Add missing @since tag [britter] JavaDoc tweaks -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-ppc64le (ppc64le) in

Re: [VOTE] Release Configuration 2.1 based on RC1

Thanks for the reviews so far. I tested with the Java 1.6 compatibility profile, and here a mvn clean install is successful (using Maven 3.3.9). Any proposals which version of the checkstyle plugin would be compatible? Or why does the checkstyle plugin becomes active for a mvn clean install at

Re: [DBCP] Release 2.2?

No attachment, try garydgregory at gmail dot com. Gary On Wed, Jul 27, 2016 at 12:03 PM, Matt Sicker wrote: > Not sure if attachments work here, but here's the generated file. It > should be the same data as in the Logging KEYS file. > > On 27 July 2016 at 11:06, Gary Gregory

Re: [VOTE] Release Configuration 2.1 based on RC1

Bummer! I have to change my vote from +1 to -1. I used Java 8 to test, which I should not have. With Java 6, it fails indeed [1]. I used: Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 05:51:28-0800) Maven home: E:\Java\apache-maven-3.0.5 Java version: 1.6.0_45,

Re: [DBCP] Release 2.2?

Not sure if attachments work here, but here's the generated file. It should be the same data as in the Logging KEYS file. On 27 July 2016 at 11:06, Gary Gregory wrote: > WRT the KEYS file, I'm not sure we can give karma without Matt being an > actual Commons Committer or

[GitHub] commons-cli pull request #7: Add an addRequiredOption method

Github user asfgit closed the pull request at: https://github.com/apache/commons-cli/pull/7 --- 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

Re: [IMAGING] Update from Java 5 to 7.

Hello Amedee, Amedee Van Gasse schrieb am Di., 26. Juli 2016 um 18:00 Uhr: > Hello Benedikt, > > Op 21-07-16 om 08:39 schreef Benedikt Ritter: > > Hallo Amedee, > > *snip* > > >> However, if the answer really is no, we will explore the other options. > >> > > > >

Re: [DBCP] Release 2.2?

WRT the KEYS file, I'm not sure we can give karma without Matt being an actual Commons Committer or a PMC member. For Nexus, I'll have to research. I think we just did this song and dance not long ago... Matt: Please send me the result of: (echo && pgp -kxa ) >> this file. (echo

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

There's a commons.release.version in the pom that looks like it's manually updated. On 27 July 2016 at 10:38, Ralph Goers wrote: > FWIW - In the Log4j build we configuration the project-info-reports-plugin > with > log4j-${Log4jReleaseVersion} > so the link on the

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

FWIW - In the Log4j build we configuration the project-info-reports-plugin with log4j-${Log4jReleaseVersion} so the link on the web site points to the eventual tag. Ralph > On Jul 27, 2016, at 8:20 AM, Benedikt Ritter wrote: > > Hello Matt. > > Matt Sicker

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

FWIW, I usually (when I do not forget) set the release date to the RC date in the changes.xml file in trunk, which then gets copied to the tag. I've never created a branch for releasing. Gary On Wed, Jul 27, 2016 at 5:43 AM, Benedikt Ritter wrote: >

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

Hello Matt. Matt Sicker schrieb am Mi., 27. Juli 2016 um 15:44 Uhr: > Can't I just svn cp from DBCP_2_2_RC1 to DBCP_2_2? Sorry, I'm more familar > with git than svn at this point. > Yes, that's what you do after a successful release vote. The problem is, that the element in

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

Can't I just svn cp from DBCP_2_2_RC1 to DBCP_2_2? Sorry, I'm more familar with git than svn at this point. On 27 July 2016 at 07:43, Benedikt Ritter wrote: > schrieb am Mi., 27. Juli 2016 um 04:53 Uhr: > > > Author: mattsicker > > Date: Wed Jul 27

Re: svn commit: r1754200 - /commons/proper/dbcp/trunk/README.md

I meant to include this in the release branch, but I somehow ended up committing some things out of order. On 27 July 2016 at 07:40, Benedikt Ritter wrote: > Hello Matt, > > I usually update the Reame.md only after the release, because it will be > live at GitHub, the moment

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

schrieb am Mi., 27. Juli 2016 um 04:53 Uhr: > Author: mattsicker > Date: Wed Jul 27 02:52:57 2016 > New Revision: 1754208 > > URL: http://svn.apache.org/viewvc?rev=1754208=rev > Log: > Creating DBCP_2_2_RC1 tag > > Added: > commons/proper/dbcp/tags/DBCP_2_2_RC1/ >

Re: svn commit: r1754200 - /commons/proper/dbcp/trunk/README.md

Hello Matt, I usually update the Reame.md only after the release, because it will be live at GitHub, the moment you commit it to trunk. People may start looking for something that has not yet been released. Regards, Benedikt schrieb am Mi., 27. Juli 2016 um 03:41 Uhr: >

Re: [VOTE] Release Configuration 2.1 based on RC1

Hello Oliver, Minor nit: Release notes talk about "Commons Configuration Package". I think this should be Apache Commons Configuration. Signs and hashes look good. Website looks good. The build fails with: $ mvn -v Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;

Re: [DBCP] Working on 2.2 RC1

Hi Matt, Matt Sicker schrieb am Mi., 27. Juli 2016 um 05:35 Uhr: > Oh, one more thing: I've uploaded a generated copy of the site from that > tag. As people.apache.org has been retired, I uploaded it to GitHub: > http://musigma.org/dbcp2-site/ home.apache.org is the new