Re: [VOTE] Apache Commons VFS 2.1 rc1

If the RM is willing, there is always the RERO route and getting a 2.1.1 out next to address JRE/JVM compat. issues if those are fixable at all from VFS in a not too hacky manner. Gary On May 5, 2016 5:41 PM, "Josh Elser" wrote: > Jörg Schaible wrote: > >> Jörg Schaible

Re: [VOTE] Apache Commons VFS 2.1 rc1

Jörg Schaible wrote: Jörg Schaible wrote: > Hi Josh, > > Josh Elser wrote: > >> Oh, well then! No pressure:) >> >> I'll have to find some time to re-read all of the conversation between >> Jörg and Stian, but my initial reaction is the same as what you were >> implying: compatibility

Re: [VOTE] Apache Commons VFS 2.1 rc1

Jörg Schaible wrote: > Hi Josh, > > Josh Elser wrote: > >> Oh, well then! No pressure :) >> >> I'll have to find some time to re-read all of the conversation between >> Jörg and Stian, but my initial reaction is the same as what you were >> implying: compatibility across more JVMs would be

Re: [VOTE] Apache Commons VFS 2.1 rc1

Hi Stian, Stian Soiland-Reyes wrote: > Thanks, I've added ${hadoop.version} so it's easier to upgrade in the > future, and also committed the of tools.jar > > > I think the maven-jar-maven JDK9 issue is due to > https://issues.apache.org/jira/browse/MJAR-206 >

Re: [VOTE] Apache Commons VFS 2.1 rc1

Hi Josh, Josh Elser wrote: > Oh, well then! No pressure :) > > I'll have to find some time to re-read all of the conversation between > Jörg and Stian, but my initial reaction is the same as what you were > implying: compatibility across more JVMs would be great, but shouldn't > block this 2.1

Re: [VOTE] Apache Commons VFS 2.1 rc1

Hi Ralph, Ralph Goers wrote: > Remember, as the release manager you get to decide whether any of this > stuff is a blocker to the release. I can tell you for sure that VFS 2.0 > wasn’t verified against this many different Java implementations and > versions. Well, you're wrong:

Re: [VOTE] Apache Commons VFS 2.1 rc1

Hi Stian, Stian Soiland-Reyes wrote: > No, it shouldn't matter the class loader content to do a normal https > connection, should it? Or do you consider that optional support from > the JDK? In that case the tests would need to test for https > capability first and ignore themselves if the JDK

Re: How to upload component site to home.apache.org for release vote?

Hello Matt, Matt Sicker schrieb am Do., 5. Mai 2016 um 21:54 Uhr: > You can use sftp or maybe eve sshfs from fuse (available on Linux and Mac > OS X, maybe Windows?). > I'm giving FileZilla a try. That should do the trick :-) Thank you! > > On 5 May 2016 at 14:33, Benedikt

Re: [LANG] Failing tests

Benedikt Ritter schrieb am Mo., 2. Mai 2016 um 12:44 Uhr: > I'm building with: > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; > 2015-11-10T17:41:47+01:00) > Maven home: /usr/local/Cellar/maven/3.3.9/libexec > Java version: 1.8.0_65, vendor: Oracle

Re: How to upload component site to home.apache.org for release vote?

You can use sftp or maybe eve sshfs from fuse (available on Linux and Mac OS X, maybe Windows?). On 5 May 2016 at 14:33, Benedikt Ritter wrote: > Hi, > > how do you upload a component site to home.apache.org? people.apache.org > hat ssh access. I always uploaded a tar via

Re: [VALIDATOR] CheckDigit implementation for German identity cards?

I wonder if we should have packages for various country codes like o.a.c.validator.de ? Then this class would go in there. Gary On Thu, May 5, 2016 at 12:46 PM, Benedikt Ritter wrote: > Benedikt Ritter schrieb am Di., 3. Mai 2016 um > 22:49 Uhr: > > >

Re: [VALIDATOR] CheckDigit implementation for German identity cards?

Benedikt Ritter schrieb am Di., 3. Mai 2016 um 22:49 Uhr: > Hello, > > I have the need for a validator implementation that can check German > identity card numbers. It's pretty simple to implement something like this > using ModulusCheckDigit. Now I'm wondering whether this

How to upload component site to home.apache.org for release vote?

Hi, how do you upload a component site to home.apache.org? people.apache.org hat ssh access. I always uploaded a tar via scp and then logged in via ssh for unpacking. home.apache.org does not have ssh access. What tools do you use to upload the component site? Benedikt

Re: [VOTE] Apache Commons VFS 2.1 rc1

Oh, well then! No pressure :) I'll have to find some time to re-read all of the conversation between Jörg and Stian, but my initial reaction is the same as what you were implying: compatibility across more JVMs would be great, but shouldn't block this 2.1 release. The other points seem to

Re: [VOTE] Apache Commons VFS 2.1 rc1

Stian Soiland-Reyes wrote: "EC AlgorithmParameters not available" seems to be a OpenJDK bug because Elastic Curves relies on the sunec native library - http://armoredbarista.blogspot.co.uk/2013/10/how-to-use-ecc-with-openjdk.html Presumably this would also fail in those JDKs? URL url = new

Re: [VFS] WIP specific release instructions

sebb wrote: On 5 May 2016 at 05:49, Josh Elser wrote: sebb wrote: Have a look at the scripts in http://svn.apache.org/viewvc/commons/scripts/ I used those for VALIDATOR and NET. Cool. Thanks for sharing. It would be good if the generic commons release documents

Re: [VFS] WIP specific release instructions

sebb wrote: On 5 May 2016 at 17:08, Ralph Goers wrote: > I really don’t know why you are making such a big deal about this. Because it's important that tags are immutable, and to to a lesser degree to avoid creating spurious snapshot builds. Yeah, it's

Re: [VFS] WIP specific release instructions

On 5 May 2016 at 17:08, Ralph Goers wrote: > I really don’t know why you are making such a big deal about this. Because it's important that tags are immutable, and to to a lesser degree to avoid creating spurious snapshot builds. > I’ve been using the maven release

Re: [VFS] WIP specific release instructions

I really don’t know why you are making such a big deal about this. I’ve been using the maven release plugin to release Log4j 2 for several years. That build was created based on the VFS 2.0 release process that also used the maven release plugin. As I have said several times, releasing VFS is

[ANNOUNCE] Apache Commons NET 3.5 released

The Apache Commons team are pleased to announce the release of Commons Net version 3.5. This is a bug fix release. All users are encouraged to upgrade to 3.5. For details of the fixes and new features please see: http://www.apache.org/dist/commons/net/RELEASE-NOTES.txt [These are also included

Re: [VOTE] Apache Commons VFS 2.1 rc1

Remember, as the release manager you get to decide whether any of this stuff is a blocker to the release. I can tell you for sure that VFS 2.0 wasn’t verified against this many different Java implementations and versions. Of course, the more testing the better! I will try to inspect the

Re: Maven Central slow to get new releases (was: [ANN] Apache Commons IO 2.5 Released)

The NET jars have finally arrived in Maven Central. However they had to do a manual sync. and CDN flush, so it's not clear when(if) the files would have arrived without manual intervention. On 5 May 2016 at 10:03, Benedikt Ritter wrote: > sebb schrieb am

Re: [VFS] WIP specific release instructions

On 5 May 2016 at 13:29, Benedikt Ritter wrote: > sebb schrieb am Do., 5. Mai 2016 um 13:55 Uhr: > >> On 5 May 2016 at 12:22, wrote: >> > Hello, >> > >> > BTW: I would use "mvn verify" instead of "mvn package" (I am not sure >> what

Re: [VFS] WIP specific release instructions

sebb schrieb am Do., 5. Mai 2016 um 13:55 Uhr: > On 5 May 2016 at 12:22, wrote: > > Hello, > > > > BTW: I would use "mvn verify" instead of "mvn package" (I am not sure > what has changed for CP40) > > CP40 changed the assembly plugin to run in the

Re: [VFS] WIP specific release instructions

On 5 May 2016 at 12:22, wrote: > Hello, > > BTW: I would use "mvn verify" instead of "mvn package" (I am not sure what > has changed for CP40) CP40 changed the assembly plugin to run in the verify phase so it can pick up any additional jars added to the package phase

Re: [VOTE] Apache Commons VFS 2.1 rc1

No, it shouldn't matter the class loader content to do a normal https connection, should it? Or do you consider that optional support from the JDK? In that case the tests would need to test for https capability first and ignore themselves if the JDK doesn't support SSL. Is this the latest IBM

Re: [VOTE] Apache Commons VFS 2.1 rc1

Thanks, I've added ${hadoop.version} so it's easier to upgrade in the future, and also committed the of tools.jar I think the maven-jar-maven JDK9 issue is due to https://issues.apache.org/jira/browse/MJAR-206 https://issues.apache.org/jira/browse/MJAR-205 so you would need to wait for

Re: [VFS] WIP specific release instructions

Hello, BTW: I would use "mvn verify" instead of "mvn package" (I am not sure what has changed for CP40) (And yes the release plugin and the commons procedure for releases is a match in hell ,) Gruss Bernd -- http://bernd.eckenfels.net -Original Message- From: Josh Elser

Re: [VOTE] Apache Commons VFS 2.1 rc1

Hi Stian, Stian Soiland-Reyes wrote: > "EC AlgorithmParameters not available" seems to be a OpenJDK bug > because Elastic Curves relies on the sunec native library - > http://armoredbarista.blogspot.co.uk/2013/10/how-to-use-ecc-with-openjdk.html > > > Presumably this would also fail in those

Re: [VOTE] Apache Commons VFS 2.1 rc1

Hi Stian, Stian Soiland-Reyes wrote: >> [ERROR] Failed to execute goal on project commons-vfs2: Could not resolve >> dependencies for project org.apache.commons:commons-vfs2:jar:2.1: Could >> not find artifact jdk.tools:jdk.tools:jar:1.6 at specified path >> /opt/oracle-jdk-

Re: [VOTE] Apache Commons VFS 2.1 rc1

"EC AlgorithmParameters not available" seems to be a OpenJDK bug because Elastic Curves relies on the sunec native library - http://armoredbarista.blogspot.co.uk/2013/10/how-to-use-ecc-with-openjdk.html Presumably this would also fail in those JDKs? URL url = new

Re: [VOTE] Apache Commons VFS 2.1 rc1

> [ERROR] Failed to execute goal on project commons-vfs2: Could not resolve > dependencies for project org.apache.commons:commons-vfs2:jar:2.1: Could not > find artifact jdk.tools:jdk.tools:jar:1.6 at specified path /opt/oracle-jdk- > bin-1.9.0.0_beta116/../lib/tools.jar -> [Help 1] > [ERROR] >

Re: US Export classification & ECCN registration for encryption in commons?

Also note that there is a TSU Exception, EAR 740.13(e) - Publicly available encryption source code - which the dev/crypto.html page says applies to the ASF. I think we need to wait for guidance from Legal. On 5 May 2016 at 10:04, Benedikt Ritter wrote: > Hi, > > Stian

Re: [VOTE] Apache Commons VFS 2.1 rc1

Test dependency should be fine. The SSHD and JSch integration is however probably not OK without classification. I think integrating with "encryption functionality" (without bundling) is sufficient to become an "encryption item":

Re: [VOTE] Apache Commons VFS 2.1 rc1

Raised as https://issues.apache.org/jira/browse/VFS-604 I'll investigate a bit with the return values to see if VFS claims the setting of permissions succeeded. noexec is a bit weird.. you are allowed to SET the executable bit (e.g. it would be correctly tar-ed up with exec flag), it just

Re: [VFS] WIP specific release instructions

Hello Josh, It's really great how much effort you're putting into this release. Thank you for that! Benedikt sebb schrieb am Do., 5. Mai 2016 um 09:57 Uhr: > On 5 May 2016 at 05:49, Josh Elser wrote: > > > > > > sebb wrote: > >> > >> Have a look at the

Re: US Export classification & ECCN registration for encryption in commons?

Hi, Stian Soiland-Reyes schrieb am Mi., 4. Mai 2016 um 14:35 Uhr: > Hi, > > Sorry for spotting this.. > > > Apache Commons Crypto is not listed on > http://www.apache.org/licenses/exports/ - does it need to be? (One > would assume so..) > > Also it was raised that Commons

Re: Maven Central slow to get new releases (was: [ANN] Apache Commons IO 2.5 Released)

sebb schrieb am Do., 5. Mai 2016 um 11:02 Uhr: > The same has happened with Commons NET. > > 10 hours and still not available from Maven Central. > > According to the issue this is supposed to have been fixed ... > > I've updated the issue (but cannot re-open it). > Thank you

Maven Central slow to get new releases (was: [ANN] Apache Commons IO 2.5 Released)

The same has happened with Commons NET. 10 hours and still not available from Maven Central. According to the issue this is supposed to have been fixed ... I've updated the issue (but cannot re-open it). S. P.S. Even if this is fixed, we should still wait 12-24 hours after publication to allow

Re: [CRYPTO] Discuss to proceed the alpha release for Commons Crypto

A release as soon as possible would be great. However, as Stian has pointed out there may be a problem with US law [1]. This should be resolved before the first release. I've created CRYPTO-54 [2] for tracking this. Regards, Benedikt [1] http://markmail.org/message/4at6msgqdxq4g4h6 [2]

RE: [CRYPTO] Discuss to proceed the alpha release for Commons Crypto

+1 for moving forwards the alpha release -Original Message- From: Sun, Dapeng [mailto:dapeng@intel.com] Sent: Thursday, May 5, 2016 4:01 PM To: Commons Developers List Subject: RE: [CRYPTO] Discuss to proceed the alpha release for Commons Crypto I'm agreed.

RE: [CRYPTO] Discuss to proceed the alpha release for Commons Crypto

I'm agreed. I think we can prepare the first release. Regards Dapeng -Original Message- From: Chen, Haifeng [mailto:haifeng.c...@intel.com] Sent: Thursday, May 05, 2016 11:21 AM To: Commons Developers List Subject: RE: [CRYPTO] Discuss to proceed the alpha release for Commons Crypto

Re: [VFS] WIP specific release instructions

On 5 May 2016 at 05:49, Josh Elser wrote: > > > sebb wrote: >> >> Have a look at the scripts in >> >> http://svn.apache.org/viewvc/commons/scripts/ >> >> I used those for VALIDATOR and NET. > > > Cool. Thanks for sharing. It would be good if the generic commons release >