Re: [crypto] The standard indentation is 4 spaces per indent

This is Commons, AND this is brand new code, so in my mind there is no "original" formatting style to respect. 4 spaces per indent like the rest of the project please. Remember that Commons is a SINGLE project. Hopefully we won't have to argue about too much about this... Gary On Apr 28, 2016

Re: [VFS] 2.1 Release Plan

Agreed but thatvis a huge job. A great goal to be sure and I am all for it. Whether that is 3.0 or 4.0 is a different issue. Gary On Apr 28, 2016 4:45 PM, "Ralph Goers" wrote: > Not to derail the conversation, but my opinion is (and has been for > several years)

[patch] Add elserj to KEYS

Can someone add my key to https://dist.apache.org/repos/dist/release/commons/KEYS, please? It would appear that I lack the required karma. Thanks in advance. - Josh Index: KEYS === --- KEYS(revision 13454) +++ KEYS

[VFS] 2.1 clirr report

It looks like there are about 7 areas in core/ where compatibility against 2.0 has been broken: * Methods added to o.a.c.v.{FileContent,FileName,FileObject} * Method added to o.a.c.v.RandomAccessContent * Parameters changed on method(s) in o.a.c.v.p.{b.Bzip2FileObject,g.GzipFileObject} *

[VFS] 2.1 release help

Ok, ran into my first issue. Seems like I don't have the karma to edit the existing JIRA issues (changing the fixVersion). Can someone please add me to the appropriate role for the project? - To unsubscribe, e-mail:

Re: [crypto] The standard indentation is 4 spaces per indent

I would prefer all Commons projects using the same style :-) sorry can't help to making some noise :-) On Thu, Apr 28, 2016 at 7:09 PM, Chen, Haifeng wrote: > Mixed whitespace styles should be definitely avoided in anyway. > Do we have to change 2 spaces indent to 4

RE: [crypto] The standard indentation is 4 spaces per indent

Mixed whitespace styles should be definitely avoided in anyway. Do we have to change 2 spaces indent to 4 spaces? Uma suggest we keep the original 2 spaces style. That makes sense. Any folks have objections? Thanks, Haifeng -Original Message- From: Matt Sicker [mailto:boa...@gmail.com]

Re: [crypto] The standard indentation is 4 spaces per indent

If you want to prevent mixed whitespace styles and whatnot, you can use EditorConfig . On 28 April 2016 at 19:06, Gangumalla, Uma wrote: > I am ok with a JIRA and type could be task for the reasons Sebb mentioned > below. > > But I prefer to

Re: [CRYPTO] Switch from JNI to JNA

This is awesome. Thanks Haifeng for driving towards 1st release. Regards, Uma On 4/26/16, 6:27 PM, "Chen, Haifeng" wrote: >Thanks folks. >An alpha release is a good suggestion! I am checking with the Spark guys >as to the Spark 2.0 code freeze timeline and check whether

Re: [crypto] The standard indentation is 4 spaces per indent

I am ok with a JIRA and type could be task for the reasons Sebb mentioned below. But I prefer to keep 2 spaces if others also ok who is going to involve in development. I assume most of Hadoop devs would have set their indentation 2 already in their IDEs. So, here also most of them would involve

Re: [VFS] 2.1 Release Plan

Not to derail the conversation, but my opinion is (and has been for several years) that VFS 3.0 should be modified to use java.nio.file.FileSystem and FileStore. I don’t think it makes much sense for VFS to have its own constructs any more. Ralph > On Apr 28, 2016, at 3:41 PM,

Re: [VFS] 2.1 Release Plan

The components have been updated multiple times. The more we modernize it (including new java version) the less useful the release will be as a drop-in replacement for 2.0. I had the impression some bug reporters would like that. (Just for the record I wondered about having an additional a

Re: [VFS] 2.1 Release Plan

Because we should make a release of the code that's ready to go now :) I think it's fine to drop 1.6 support, but if it's going to involve more code changes, I don't think it should happen for 2.1. If it's just a matter of tweaking the compiler-plugin, that's fine. I hope to look at this all

CP 40?

Did we give up on releasing CP 40? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition Spring Batch in Action

Re: [VFS] 2.1 Release Plan

Why don't we bring [vfs] 2.1 from Java 6 to 7 and update 3rd party components? Gary On Tue, Apr 26, 2016 at 12:36 PM, Gary Gregory wrote: > Yes, there is a BC breakage for providers, is that grounds for a package > and Maven coordinate rename to vfs3? > > Gary > > On

Re: [io] Make requirement Java 7?

trunk is now Java 7 in the POM. Gary On Thu, Apr 28, 2016 at 5:44 AM, Benedikt Ritter wrote: > Kristian Rosenvold schrieb am Do., 28. Apr. > 2016 um 11:59 Uhr: > > > 2016-04-26 15:39 GMT+02:00 Emmanuel Bourg : > > > > > We

Re: [VOTE] Release Validator 1.5.1 based on RC2

Note a blocker: Missing text in @link: * Note: the {@link #isValid(String)} and {@link } methods strip off any leading +1 Release notes, MD5, SHA1, ASC, all OK. Builds OK from src zip with the expected Slf4j report blow ups with: Apache Maven *3.3.9* (bb52d8502b132ec0a5a3f4c09453c07478323dc5;

Re: [VOTE] Release Validator 1.5.1 based on RC2

Le 25/04/2016 à 23:24, sebb a écrit : > [X] +1 Release these artifacts Tested on Debian with Maven 3.3.9 and OpenJDK 8. Builds fine from the tag and from the source archive. The changes look good. Emmanuel Bourg signature.asc Description: OpenPGP digital signature

Re: [ALL] Validator vote - please

AFK most of the day. I started reviewing and got side tracked on day 1 of the vote. Will continue tomorrow most likely. Gary On Apr 28, 2016 6:23 AM, "sebb" wrote: > The Validator vote has been open 3 days now, with no votes or even > comments. > > Please could some other PMC

Re: [ALL] Validator vote - please

I'm giving an on site Java Training at one of our customers currently. I'll have some time this evening and I've already planed to use that time to verify this release. Thank you! Benedikt sebb schrieb am Do., 28. Apr. 2016 um 15:23 Uhr: > The Validator vote has been open 3

[ALL] Validator vote - please

The Validator vote has been open 3 days now, with no votes or even comments. Please could some other PMC members vote? Thanks! - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail:

Re: [VOTE] Release Validator 1.5.1 based on RC2

On 25 April 2016 at 22:24, sebb wrote: > Second try: > > Validator 1.5.1 RC2 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/validator/1.5.1_RC2/ > (revision 13418) > >

Re: [io] Make requirement Java 7?

Kristian Rosenvold schrieb am Do., 28. Apr. 2016 um 11:59 Uhr: > 2016-04-26 15:39 GMT+02:00 Emmanuel Bourg : > > > We are not alone :) RedHat is still maintaining OpenJDK 6 and providing > > security fixes for things like critical production

Re: [io] Make requirement Java 7?

2016-04-26 15:39 GMT+02:00 Emmanuel Bourg : > We are not alone :) RedHat is still maintaining OpenJDK 6 and providing > security fixes for things like critical production systems not meant to > be changed every two years. > > Yes, and they are getting paid for it. If they need

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