RE: [jira] [Updated] (CRYPTO-31) Make fields final wherever possible

Hi Gary, Thank you for pointing it out. I will remove the tag of 'affects version'. Regards Dapeng -Original Message- From: Gary Gregory [mailto:garydgreg...@gmail.com] Sent: Thursday, April 28, 2016 1:03 PM To: Commons Developers List Subject: Re: [jira] [Updated] (CRYPTO-31) Make fiel

Re: [jira] [Updated] (CRYPTO-31) Make fields final wherever possible

I do not think tickets should be marked as affects 1.0.0 since that version is not released. Gary On Apr 27, 2016 8:33 PM, "Dapeng Sun (JIRA)" wrote: > > [ > https://issues.apache.org/jira/browse/CRYPTO-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Dapeng Sun

Jenkins build is back to normal : Commons-CRYPTO #16

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

Re: [VFS] 2.1 Release Plan

On 27 April 2016 at 17:18, Ralph Goers wrote: > One thing to be wary of - Most, if not all, of the other Commons projects are > not multi-module projects. I remember specifically having to do “interesting” > things in the VFS pom to fix things that didn’t work correctly in > commons-parent. I a

Re: [VFS] 2.1 Release Plan

No worries. I am very familiar with fixing goofed-up Maven projects. The warning is appreciated. Ralph Goers wrote: One thing to be wary of - Most, if not all, of the other Commons projects are not multi-module projects. I remember specifically having to do “interesting” things in the VFS pom

Re: [VFS] 2.1 Release Plan

One thing to be wary of - Most, if not all, of the other Commons projects are not multi-module projects. I remember specifically having to do “interesting” things in the VFS pom to fix things that didn’t work correctly in commons-parent. I am sure over the course of time a lot of that has change

Re: [VFS] 2.1 Release Plan

Thanks, Sebb and Ralph. I can dig through the parent poms. I wouldn't have initially realized that there was a "commons" parent pom. Thanks for pointing that out. sebb wrote: On 27 April 2016 at 05:58, Ralph Goers wrote: As I recall, I performed the VFS 2.0 release. I did use the Maven rele

Re: [VFS] 2.1 Release Plan

Hello, see inline. Am Tue, 26 Apr 2016 18:05:01 -0400 schrieb Josh Elser: Thanks for the great details, Bernd. Some questions/comments: I hadn't even stumbled across VFS-570 due to its lack of fixVersion=2.1. Are there more that need to be correctly tagged which could potentially block the re

Re: [VFS] 2.1 Release Plan

On 27 April 2016 at 05:58, Ralph Goers wrote: > As I recall, I performed the VFS 2.0 release. I did use the Maven release > plugin. It has been so long that I have forgotten the details of what had to > be done, but I know I ended up using it as the model for setting up Log4j 2’s > build. > > A

Build failed in Jenkins: Commons-CRYPTO #15

See Changes: [sdp] CRYPTO-36: Fix crypto web link -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-5 (docker Ubuntu ubuntu5 ubuntu yahoo-not-