Re: [VFS] WIP specific release instructions

2016-05-04 Thread Josh Elser



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 referenced these if they are expected to be re-used by 
other commons projects' RMs.



On 4 May 2016 at 04:43, Josh Elser  wrote:

Here's what I've been doing. The generic instructions are woefully
incomplete (before someone chimes in again - no, not just because "VFS is a
multi-module project"). I think I have this on point for rc1, so I'm writing
it down here before I forget (we can figure out where it *should* go later).

rc0 only:
# Make the branch
$ svn cp trunk branches/VFS-XXX
$ cd branches/VFS-XXX
# Set the proper versions
$ mvn release:prepare


We use a tag not a branch, but perhaps that is what the release plugin does.
In which case I assume the branch is taken to avoid mangling trunk?


release:prepare doesn't do the tagging (this is what release:perform 
does). All it's really doing are some pre-condition checks and version 
updates. TBQH, I don't have any idea how the maven-release-plugin and 
SVN are remotely useful for the ASF's vote-then-promote process.


That said, it's ok if I don't get it. This is what worked for me and I'm 
happy with it. If there's something obvious I could have done 
differently, great.



---

# Or just set it to your JDK6 installation -- this works on OSX
$ export JAVA_HOME=$(/usr/libexec/java_home -v1.6)

# Where ${asf.username} for me is "elserj"
$ mvn clean package -Duser.name=${asf.username}


No need to use package if using CP40


What are you using instead of `package` to build the code...




# Set back to 1.7 because my 1.6 installation has trouble deploying to nexus
$ export JAVA_HOME=$(/usr/libexec/java_home -v1.7)


So does mine; in which case use -Pjava-1.6 below.


$ mvn deploy -Prelease -Duser.name=${asf.username}

# This is what could be consolidated via one invocation of `mvn site`
$ mvn site:site site:stage

# Move back to the root SVN repo
$ cd ../..
$ svn cp branches/VFS-XXX tags/commons-vfs-project-XXX-rcN


Isn't that what the release plugin does?

You might find

http://svn.apache.org/viewvc/commons/scripts/create_RC_tag.sh

easier to use - it does it all for you without needing to create a
temporary branch.


Cool. I didn't find these from the generic commons release document.


--

Things not covered above:

* Copying artifacts (tarballs/zips, xsums, and sigs) into
dist.a.o/dev/commons/... (building md5/sha1 files)
* Closing staging repo in Nexus


That can be done using Nexus2DistDev.sh


Again, great. It would have been good to know about these beforehand.




--

Some things that could still be improved that I didn't fix:

* Artifacts in dist/target are renamed when they're installed/deployed, but
not in the local directory. Should do a rename of the file on disk so that
what is on the RM's computer matches what is in their m2 repo and ASF nexus.


Or ignore the local copies and use Nexus2DistDev.sh which copies the
bin/src artifacts from Nexus and deploys to dist/dev and can remove
them from Nexus before closing the staging repo.

AFAIK only the deploy directory (i.e. Nexus) has the hashes.


* `mvn site` which invokes site:site and site:stage automatically (which
would make for a more natural build process -- `mvn deploy` would build the
site automatically)


I don't follow that.


`mvn site` is invoking the "site" maven lifecycle phase. "mvn site:site` 
and `mvn site:stage` are invoking executions on the maven-site-plugin. 
These are two distinct kinds of actions. We can configure the 
maven-site-plugin (and/or other necessary tasks) to run at the 'site' 
lifecycle phase for a more 'natural' process.





Again, for now, this is just for my benefit. When this is all over, I'll try
to add this all to the website. Please point out anything wrong/missing.
Thanks.

- Josh

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



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



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



Re: [VOTE] Apache Commons VFS 2.1 rc1

2016-05-04 Thread Josh Elser

Thanks for investigating and sharing your findings, Jörg!

I guess commons-vfs has some room for improvement on IBM JDKs. I have 
been using Oracle JDK6/7 here locally which has been fine. I think this 
would be great to investigate further for future releases.


Jörg Schaible wrote:

Hi,

I've tried to build the release from the source tarball using my compiler
zoo.

Passes:
  - Sun JDK 1.6
  - IcedTea/OpenJDK 6
  - Oracle JDK 1.7
  - IcedTea/OpenJDK 7
  - Oracle JDK 1.8

Tests fail with IBM JDKs 1.6 and 1.7, IcedTea/OpenJDK 3 and Java 9:

= %<  ==
$ mvn-3.2 -version
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
2014-12-14T18:29:23+01:00)
Maven home: /usr/share/maven-bin-3.2
Java version: 1.6.0, vendor: IBM Corporation
Java home: /opt/ibm-jdk-bin-1.6.0.9_p2/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.6-gentoo", arch: "amd64", family: "unix"
= %<  ==
Failed tests:
org.apache.commons.vfs2.impl.test.VfsClassLoaderTests.testGetResourcesJARs(org.apache.commons.vfs2.impl.test.VfsClassLoaderTests)
   Run 1: PASS
   Run 2: PASS
   Run 3: PASS
   Run 4: PASS
   Run 5: PASS
   Run 6: PASS
   Run 7: PASS
   Run 8: PASS
   Run 9: VfsClassLoaderTests>AbstractProviderTestCase.runTest:218-

testGetResourcesJARs:154 First resource must refer to nested.jar but was

jar:file:/opt/ibm-jdk-
bin-1.6.0.9_p2/jre/lib/amd64/default/jclSC160/vm.jar!/META-INF/MANIFEST.MF
   Run 10: PASS
   Run 11: PASS
   Run 12: PASS
   Run 13: PASS
   Run 14: PASS
   Run 15: PASS
   Run 16: PASS
   Run 17: PASS
   Run 18: PASS
   Run 19: PASS
   Run 20: PASS
   Run 21: PASS
   Run 22: PASS
   Run 23: PASS
   Run 24: PASS
   Run 25: PASS
= %<  ==
$ mvn -version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T17:41:47+01:00)
Maven home: /usr/share/maven-bin-3.3
Java version: 1.7.0, vendor: IBM Corporation
Java home: /opt/ibm-jdk-bin-1.7.0.5/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.6-gentoo", arch: "amd64", family: "unix"
= %<  ==
Failed tests:
org.apache.commons.vfs2.impl.test.VfsClassLoaderTests.testGetResourcesJARs(org.apache.commons.vfs2.impl.test.VfsClassLoaderTests)
   Run 1: PASS
   Run 2: PASS
   Run 3: PASS
   Run 4: PASS
   Run 5: PASS
   Run 6: PASS
   Run 7: PASS
   Run 8: PASS
   Run 9: VfsClassLoaderTests>AbstractProviderTestCase.runTest:218-

testGetResourcesJARs:154 First resource must refer to nested.jar but was

jar:file:/opt/ibm-jdk-
bin-1.7.0.5/jre/lib/amd64/compressedrefs/jclSC170/vm.jar!/META-
INF/MANIFEST.MF
   Run 10: PASS
   Run 11: PASS
   Run 12: PASS
   Run 13: PASS
   Run 14: PASS
   Run 15: PASS
   Run 16: PASS
   Run 17: PASS
   Run 18: PASS
   Run 19: PASS
   Run 20: PASS
   Run 21: PASS
   Run 22: PASS
   Run 23: PASS
   Run 24: PASS
   Run 25: PASS
= %<  ==
$ mvn -version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T17:41:47+01:00)
Maven home: /usr/share/maven-bin-3.3
Java version: 1.8.0_77, vendor: Oracle Corporation
Java home: /opt/icedtea-bin-3.0.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.6-gentoo", arch: "amd64", family: "unix"
= %<  ==
Tests in error:
   GetContentInfoFunctionalTest.testGoogle:76 » FileSystem Unknown message
with code "java.lang.RuntimeException:
java.security.NoSuchAlgorithmException: EC AlgorithmParameters not
available".
 at
org.apache.commons.vfs2.provider.http.HttpFileContentInfoFactory.create(HttpFileContentInfoFactory.java:51)
 at
org.apache.commons.vfs2.provider.DefaultFileContent.getContentInfo(DefaultFileContent.java:806)
 at
org.apache.commons.vfs2.provider.https.test.GetContentInfoFunctionalTest.testGoogle(GetContentInfoFunctionalTest.java:76)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at 

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

2016-05-04 Thread Chen, Haifeng
Sorry for the typo in the second paragraph.

Hi,
After weeks of collaborated work from the community, the renaming, building, 
API refactoring and documentation are almost done.
Much thanks to the Commons community for all your support.

The community folks proposed to go with an alpha release if we want sooner. So 
I suggest we can proceed the alpha release now.
Please feel free to share your opinion.

If there is no objection, we will proceed to prepare the release artifacts and 
send out the release VOTE to the community when ready.

Regards,
Haifeng


From: Chen, Haifeng
Sent: Thursday, May 5, 2016 11:18 AM
To: Commons Developers List 
Subject: [CRYPTO] Discuss to proceed the alpha release for Commons Crypto

Hi,
After weeks of collaborated work from the community, the renaming, building, 
API refactoring and documentation are almost done.
Much thanks to the Commons community for all your support.

The community folks to prepare an alpha release if we want sooner. So I suggest 
we can proceed the alpha release now.
Please feel free to share your opinion.

If there is no objection, we will proceed to prepare the release artifacts and 
send out the release VOTE to the community when ready.

Regards,
Haifeng


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

2016-05-04 Thread Chen, Haifeng
Hi,
After weeks of collaborated work from the community, the renaming, building, 
API refactoring and documentation are almost done.
Much thanks to the Commons community for all your support.

The community folks to prepare an alpha release if we want sooner. So I suggest 
we can proceed the alpha release now.
Please feel free to share your opinion.

If there is no objection, we will proceed to prepare the release artifacts and 
send out the release VOTE to the community when ready.

Regards,
Haifeng


[RESULT][VOTE] Commons NET 3.5 based on RC3

2016-05-04 Thread sebb
Thanks to all who tested the RC and voted; here are the results:

Stian Soiland-Reyes +1 (non-binding)
Gary Gregory +1 (binding)
Oliver Heger +1 (binding)
Benedikt Ritter +1 (binding)
Jörg Schaible +1 (binding)

There being at least 3 binding +1 votes and more +1 than -1 the vote passes.

I will proceed with the release.


-- Forwarded message --
From: sebb 
Date: 2 May 2016 at 00:12
Subject: [VOTE] Commons NET 3.5 based on RC3
To: CommonsDev 


Try again.

==

NET 3.5 RC3 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/net/3.5_RC3/ (13489)

commons-net-3.5-bin.tar.gz.sha1:4941d802a78dd198786d4f6a0a9500f658f44a85
commons-net-3.5-bin.zip.sha1:b03fc180862aff92de7aaa6ca94b83ef7f3435cf
commons-net-3.5-src.tar.gz.sha1:1215a0df6fe67cc2671679f58b29dede752f232d
commons-net-3.5-src.zip.sha1:ea576c3a5f7d83d037e0ee9dcedb98a5ac076c1a

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1158/commons-net/commons-net/3.5/

These are the artifacts and their hashes

commons-net-3.5-test-sources.jar
(SHA1: 5172e1c4f6544eb7755f034c89b812714fead83d)
commons-net-3.5-sources.jar
(SHA1: 185dea3736a8583323da4d6ce647719ddf452ccf)
commons-net-3.5-ftp.jar
(SHA1: 6e28fe5e21df8e2b1f166f85d69820f844c0d48e)
commons-net-3.5.jar
(SHA1: 342fc284019f590e1308056990fdb24a08f06318)
commons-net-3.5-examples.jar
(SHA1: 6272d80e897347c3c5f3691c8d76eae5deb764e1)
commons-net-3.5-tests.jar
(SHA1: b8925a81e0e7ed09e81341f17f1408dd6fec6f43)
commons-net-3.5.pom
(SHA1: d0306becf8a919442cf01a925ffaadd67dead3cf)
commons-net-3.5-javadoc.jar
(SHA1: 72850d3da769c0ea7b7dad00da52b7912140aee0)


Details of changes since 3.4 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/net/3.5_RC3/RELEASE-NOTES.txt
http://home.apache.org/~sebb/net-3.5-RC3/changes-report.html

  I have tested this with JDK 1.6, 7, 8 using Apache Maven 3.3.9

Note: Maven 3.1.1 works too, but has problems with the Nexus deploy -
peer not authenticated
Maven 3.2.5 also fails to deploy - Could not generate DH keypair

  The tag is here:
http://svn.apache.org/repos/asf/commons/proper/net/tags/NET_3_5_RC3/
(1741905)

  Site:
http://home.apache.org/~sebb/net-3.5-RC3/
   (some *relative* links are broken - these will be OK once the site
is deployed)

  Clirr Report (compared to 3.4):
http://home.apache.org/~sebb/net-3.5-RC3/clirr-report.html

  RAT Report:
http://home.apache.org/~sebb/net-3.5-RC3/rat-report.html

  KEYS:
  https://www.apache.org/dist/commons/KEYS

  Please review the release candidate and vote.
  This vote will close no sooner than 72 hours from now,
  i.e. sometime after 23:30 GMT 4 May 2016


  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

  Thanks!

  Sebb

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



Re: [VOTE] Apache Commons VFS 2.1 rc1

2016-05-04 Thread Jörg Schaible
e...@zusammenkunft.net wrote:

> Hello,
> 
> Java 9 is not supported (only 8)

The build with Java 9 is a heads-up. However, vfs 2.0 was release when Java 
7 was one month old ...

> , for the other problems I am not sure, do
> you consider that an blocker?

This depends actually on the cause. Currently I simply report those tests as 
failing and therefore I do not vote.

Cheers,
Jörg


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



Re: [VOTE] Apache Commons VFS 2.1 rc1

2016-05-04 Thread ecki
Hello,

Java 9 is not supported (only 8), for the other problems I am not sure, do you 
consider that an blocker?

Gruss
Bernd

-- 
http://bernd.eckenfels.net

-Original Message-
From: "Jörg Schaible" 
To: dev@commons.apache.org
Sent: Do., 05 Mai 2016 0:39
Subject: Re: [VOTE] Apache Commons VFS 2.1 rc1

Hi,

I've tried to build the release from the source tarball using my compiler 
zoo.

Passes:
 - Sun JDK 1.6
 - IcedTea/OpenJDK 6
 - Oracle JDK 1.7
 - IcedTea/OpenJDK 7
 - Oracle JDK 1.8

Tests fail with IBM JDKs 1.6 and 1.7, IcedTea/OpenJDK 3 and Java 9:

= %< ==
$ mvn-3.2 -version
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 
2014-12-14T18:29:23+01:00)
Maven home: /usr/share/maven-bin-3.2
Java version: 1.6.0, vendor: IBM Corporation
Java home: /opt/ibm-jdk-bin-1.6.0.9_p2/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.6-gentoo", arch: "amd64", family: "unix"
= %< ==
Failed tests: 
org.apache.commons.vfs2.impl.test.VfsClassLoaderTests.testGetResourcesJARs(org.apache.commons.vfs2.impl.test.VfsClassLoaderTests)
  Run 1: PASS
  Run 2: PASS
  Run 3: PASS
  Run 4: PASS
  Run 5: PASS
  Run 6: PASS
  Run 7: PASS
  Run 8: PASS
  Run 9: VfsClassLoaderTests>AbstractProviderTestCase.runTest:218-
>testGetResourcesJARs:154 First resource must refer to nested.jar but was 
jar:file:/opt/ibm-jdk-
bin-1.6.0.9_p2/jre/lib/amd64/default/jclSC160/vm.jar!/META-INF/MANIFEST.MF
  Run 10: PASS
  Run 11: PASS
  Run 12: PASS
  Run 13: PASS
  Run 14: PASS
  Run 15: PASS
  Run 16: PASS
  Run 17: PASS
  Run 18: PASS
  Run 19: PASS
  Run 20: PASS
  Run 21: PASS
  Run 22: PASS
  Run 23: PASS
  Run 24: PASS
  Run 25: PASS
= %< ==
$ mvn -version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-10T17:41:47+01:00)
Maven home: /usr/share/maven-bin-3.3
Java version: 1.7.0, vendor: IBM Corporation
Java home: /opt/ibm-jdk-bin-1.7.0.5/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.6-gentoo", arch: "amd64", family: "unix"
= %< ==
Failed tests: 
org.apache.commons.vfs2.impl.test.VfsClassLoaderTests.testGetResourcesJARs(org.apache.commons.vfs2.impl.test.VfsClassLoaderTests)
  Run 1: PASS
  Run 2: PASS
  Run 3: PASS
  Run 4: PASS
  Run 5: PASS
  Run 6: PASS
  Run 7: PASS
  Run 8: PASS
  Run 9: VfsClassLoaderTests>AbstractProviderTestCase.runTest:218-
>testGetResourcesJARs:154 First resource must refer to nested.jar but was 
jar:file:/opt/ibm-jdk-
bin-1.7.0.5/jre/lib/amd64/compressedrefs/jclSC170/vm.jar!/META-
INF/MANIFEST.MF
  Run 10: PASS
  Run 11: PASS
  Run 12: PASS
  Run 13: PASS
  Run 14: PASS
  Run 15: PASS
  Run 16: PASS
  Run 17: PASS
  Run 18: PASS
  Run 19: PASS
  Run 20: PASS
  Run 21: PASS
  Run 22: PASS
  Run 23: PASS
  Run 24: PASS
  Run 25: PASS
= %< ==
$ mvn -version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-10T17:41:47+01:00)
Maven home: /usr/share/maven-bin-3.3
Java version: 1.8.0_77, vendor: Oracle Corporation
Java home: /opt/icedtea-bin-3.0.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.6-gentoo", arch: "amd64", family: "unix"
= %< ==
Tests in error: 
  GetContentInfoFunctionalTest.testGoogle:76 » FileSystem Unknown message 
with code "java.lang.RuntimeException: 
java.security.NoSuchAlgorithmException: EC AlgorithmParameters not 
available".
at 
org.apache.commons.vfs2.provider.http.HttpFileContentInfoFactory.create(HttpFileContentInfoFactory.java:51)
at 
org.apache.commons.vfs2.provider.DefaultFileContent.getContentInfo(DefaultFileContent.java:806)
at 
org.apache.commons.vfs2.provider.https.test.GetContentInfoFunctionalTest.testGoogle(GetContentInfoFunctionalTest.java:76)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at 

Re: [VOTE] Apache Commons VFS 2.1 rc1

2016-05-04 Thread Jörg Schaible
Hi,

I've tried to build the release from the source tarball using my compiler 
zoo.

Passes:
 - Sun JDK 1.6
 - IcedTea/OpenJDK 6
 - Oracle JDK 1.7
 - IcedTea/OpenJDK 7
 - Oracle JDK 1.8

Tests fail with IBM JDKs 1.6 and 1.7, IcedTea/OpenJDK 3 and Java 9:

= %< ==
$ mvn-3.2 -version
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 
2014-12-14T18:29:23+01:00)
Maven home: /usr/share/maven-bin-3.2
Java version: 1.6.0, vendor: IBM Corporation
Java home: /opt/ibm-jdk-bin-1.6.0.9_p2/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.6-gentoo", arch: "amd64", family: "unix"
= %< ==
Failed tests: 
org.apache.commons.vfs2.impl.test.VfsClassLoaderTests.testGetResourcesJARs(org.apache.commons.vfs2.impl.test.VfsClassLoaderTests)
  Run 1: PASS
  Run 2: PASS
  Run 3: PASS
  Run 4: PASS
  Run 5: PASS
  Run 6: PASS
  Run 7: PASS
  Run 8: PASS
  Run 9: VfsClassLoaderTests>AbstractProviderTestCase.runTest:218-
>testGetResourcesJARs:154 First resource must refer to nested.jar but was 
jar:file:/opt/ibm-jdk-
bin-1.6.0.9_p2/jre/lib/amd64/default/jclSC160/vm.jar!/META-INF/MANIFEST.MF
  Run 10: PASS
  Run 11: PASS
  Run 12: PASS
  Run 13: PASS
  Run 14: PASS
  Run 15: PASS
  Run 16: PASS
  Run 17: PASS
  Run 18: PASS
  Run 19: PASS
  Run 20: PASS
  Run 21: PASS
  Run 22: PASS
  Run 23: PASS
  Run 24: PASS
  Run 25: PASS
= %< ==
$ mvn -version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-10T17:41:47+01:00)
Maven home: /usr/share/maven-bin-3.3
Java version: 1.7.0, vendor: IBM Corporation
Java home: /opt/ibm-jdk-bin-1.7.0.5/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.6-gentoo", arch: "amd64", family: "unix"
= %< ==
Failed tests: 
org.apache.commons.vfs2.impl.test.VfsClassLoaderTests.testGetResourcesJARs(org.apache.commons.vfs2.impl.test.VfsClassLoaderTests)
  Run 1: PASS
  Run 2: PASS
  Run 3: PASS
  Run 4: PASS
  Run 5: PASS
  Run 6: PASS
  Run 7: PASS
  Run 8: PASS
  Run 9: VfsClassLoaderTests>AbstractProviderTestCase.runTest:218-
>testGetResourcesJARs:154 First resource must refer to nested.jar but was 
jar:file:/opt/ibm-jdk-
bin-1.7.0.5/jre/lib/amd64/compressedrefs/jclSC170/vm.jar!/META-
INF/MANIFEST.MF
  Run 10: PASS
  Run 11: PASS
  Run 12: PASS
  Run 13: PASS
  Run 14: PASS
  Run 15: PASS
  Run 16: PASS
  Run 17: PASS
  Run 18: PASS
  Run 19: PASS
  Run 20: PASS
  Run 21: PASS
  Run 22: PASS
  Run 23: PASS
  Run 24: PASS
  Run 25: PASS
= %< ==
$ mvn -version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-10T17:41:47+01:00)
Maven home: /usr/share/maven-bin-3.3
Java version: 1.8.0_77, vendor: Oracle Corporation
Java home: /opt/icedtea-bin-3.0.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.6-gentoo", arch: "amd64", family: "unix"
= %< ==
Tests in error: 
  GetContentInfoFunctionalTest.testGoogle:76 » FileSystem Unknown message 
with code "java.lang.RuntimeException: 
java.security.NoSuchAlgorithmException: EC AlgorithmParameters not 
available".
at 
org.apache.commons.vfs2.provider.http.HttpFileContentInfoFactory.create(HttpFileContentInfoFactory.java:51)
at 
org.apache.commons.vfs2.provider.DefaultFileContent.getContentInfo(DefaultFileContent.java:806)
at 
org.apache.commons.vfs2.provider.https.test.GetContentInfoFunctionalTest.testGoogle(GetContentInfoFunctionalTest.java:76)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at 

Re: [ANNOUNCE] Commons Parent 40 released

2016-05-04 Thread Jörg Schaible
Just a heads-up: Due to missing signature of the animal sniffer for Java 9 
you have to run maven with option -Danimal.sniffer.skip to build with a 
recent Java 9.

sebb wrote:

> Commons Parent 40 has been released.
> [It may take a few hours before the artifacts are available from Maven
> [Central]
> 
> The release updates plugins and Apache parent pom version.
> It fixes COMMONSSITE-87 and COMMONSSITE-82.
> 
> N.B. The assembly plugin now runs in the verify phase (it was
> previously run in the package phase). See COMMONSSITE-87.
> 
> This allows child poms to create additional jars to be added to the
> assembly. The deploy phase will now pick up the jars without needing to
> run the package phase.
> The change will affect child poms that rely on the assembly occurring
> in the package phase.
> They will need to be amended to use the verify phase instead.
> 
> Main Changes:
> o Update Apache Parent POM : 16 -> 17
> o COMMONSSITE-87 - ensure assembly plugin runs after all package phase
> plugins o COMMONSSITE-82 - use Commons Skin 4.1 (site.xml)
> o Require minimum of Maven 3.0.5
> 
> Release Notes are at:
> 
> http://svn.apache.org/repos/asf/commons/proper/commons-parent/tags/commons-parent-40/RELEASE-NOTES.txt
> 
> The documentation for the POM is at:
> 
> http://commons.apache.org/commons-parent-pom.html
> 
> Please report (or just fix - can be done using CMS) any doc errors and
> omissions.
> 
> Note: components are recommended to upgrade to this version, but this
> is not mandatory, so if it causes problems, please revert to the
> original version - and report the problems on the mailing list or in
> JIRA under COMMONSSITE
> 
> 
> Enjoy!



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



Re: [VOTE] Apache Commons VFS 2.1 rc1

2016-05-04 Thread Bernd Eckenfels
Thanks Stian!

Do you plan to report the noexec issue? If not let me know and I will
file one.

I thought we already had one but I cant find it.

I will do some windows tests and then vote.

Gruss
Bernd

 Am Wed, 4 May 2016 13:28:54 +0100
schrieb Stian Soiland-Reyes :

> +1 (non-binding)
> 
> +1 signatures
> +1 hashes
> +1 LICENSE, NOTICE
> 0 README.md says 2.0
> 0 Extra README.txt (confusing)
> +1 RELEASE-NOTES.txt
> +1 mvn apache-rat:check
> +1 maven repository signatures/hashes
> +1 maven repository *distribution* matches dist/
> 0 mvn clean install OK (but 1 test fails on tmpfs)
> +1 target/*jar matches binaries
> +1 source matches svn tag (minus sandbox/ :-) )
> +1 Dependency licenses OK
> -1 Unclassified use of encryption libraries Bouncy Castle/Apache
> Mina/SSHD/Hadoop/jsch/Jetty (plus some AES128 in DefaultCryptor) - but
> Commons VFS is not classified on
> http://www.apache.org/licenses/exports/
> 
> I won't take a stand on the US Export classification requirement as
> https://issues.apache.org/jira/browse/LEGAL-250 has not been resolved
> yet.
> 
> 
> I get this test error (because my /tmp is mounted with noexec):
> 
> Tests run: 90, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.259
> sec <<< FAILURE! - in
> org.apache.commons.vfs2.provider.local.test.LocalProviderTestCase
> testExecutable(org.apache.commons.vfs2.test.PermissionsTests)  Time
> elapsed: 0.011 sec  <<< FAILURE!
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.commons.vfs2.test.PermissionsTests.testExecutable(PermissionsTests.java:70)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498) at
> org.apache.commons.vfs2.test.AbstractProviderTestCase.runTest(AbstractProviderTestCase.java:218)
> at junit.framework.TestCase.runBare(TestCase.java:141) at
> junit.framework.TestResult$1.protect(TestResult.java:122) at
> junit.framework.TestResult.runProtected(TestResult.java:142) at
> junit.framework.TestResult.run(TestResult.java:125) at
> junit.framework.TestCase.run(TestCase.java:129) at
> junit.framework.TestSuite.runTest(TestSuite.java:252) at
> junit.framework.TestSuite.run(TestSuite.java:247) at
> junit.extensions.TestDecorator.basicRun(TestDecorator.java:23) at
> org.apache.commons.vfs2.test.AbstractTestSuite$1.protect(AbstractTestSuite.java:149)
> at junit.framework.TestResult.runProtected(TestResult.java:142) at
> org.apache.commons.vfs2.test.AbstractTestSuite.run(AbstractTestSuite.java:154)
> 
> Building from /var/tmp worked.
> 
> I won't fail because of this - I'm probably special still using tmpfs
> :)   (And adding conditional testing would mean using the same APIs or
> requivalent Java 7 NIO files APIs to see if executable bit is
> supported).
> 
> 
> Checked with:
> 
> stain@biggie:/tmp/vfs/source/commons-vfs-2.1$ mvn -v
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-10T16:41:47+00:00)
> Maven home: /home/stain/software/maven
> Java version: 1.8.0_72-internal, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "3.16.0-67-generic", arch: "amd64",
> family: "unix"
> 
> On 4 May 2016 at 04:43, Josh Elser  wrote:
> > All,
> >
> > Please consider the following for Apache Commons VFS2 version 2.1
> > (rc1).
> >
> > Maven repository:
> > https://repository.apache.org/content/repositories/orgapachecommons-1163
> > Artifacts: https://dist.apache.org/repos/dist/dev/commons/vfs/
> > r13511
> >
> > MD5  commons-vfs-distribution-2.1-bin.tar.gz
> > 1192914d1ba6f8ca3a2a688feeff602c
> > SHA1 commons-vfs-distribution-2.1-bin.tar.gz
> > 285097f1db6cbc9d76ae5bb3adf66a315344a864
> > MD5  commons-vfs-distribution-2.1-src.tar.gz
> > 0646187562302a7dcfbddb93204fc9eb
> > SHA1 commons-vfs-distribution-2.1-src.tar.gz
> > 24bab87fd4049b9389acd1b6e272f405630aeb25
> > MD5  commons-vfs-distribution-2.1-bin.zip
> > 3785874aa0cda64d68acbb8fb7db8bea SHA1
> > commons-vfs-distribution-2.1-bin.zip
> > 942a23fb202b89b1a8432beeb0a66469959e661d MD5
> > commons-vfs-distribution-2.1-src.zip
> > c8ef43d308bed1b3ffcb363c15285176 SHA1
> > commons-vfs-distribution-2.1-src.zip
> > 1ddf0d218f659766f136894eab0beca504ab9f8c
> >
> > Signed with 4677D66C from
> > https://dist.apache.org/repos/dist/release/commons/KEYS
> >
> > SVN tag is available at
> > https://svn.apache.org/repos/asf/commons/proper/vfs/tags/commons-vfs-project-2.1-RC1/
> > r1742212
> >
> > Staged Maven website:
> > http://home.apache.org/~elserj/commons/commons-vfs-2.1/
> >
> > All reports are available in the provided staged Maven site (see
> > 

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

2016-05-04 Thread sebb
On 4 May 2016 at 13:35, Stian Soiland-Reyes  wrote:
> 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 VFS depends on Bouncy Castle/Apache
> Mina/Jetty/SSHD/Hadoop/jsch and has encryption binding for AES128 -
> perhaps that also needs to be listed and registered?
>
>
> We only have listed:
>
> Commons Compress
> Commons OpenPGP
>
>
> See guidance on
> http://www.apache.org/dev/crypto.html
>
>
> BTW - I've raised https://issues.apache.org/jira/browse/LEGAL-250 to
> see if merely using a listed source as a Maven  means you
> also are classified - or if you would need to also bundle the
> dependency's binary (which I think we don't do).

It does not matter if the dependency is bundled or not.

The page says:

" ASF product distributions that contain or are "specially designed"
to use cryptography."

AFAIK:
Compress contains some decryption
OpenPGP is "specially designed" to use cryptography.

I assume the same is true of Crypto.

But note that the rules changed in 2010; the page has yet to be updated.

>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/-0001-9842-9718
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

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



Re: [VFS] WIP specific release instructions

2016-05-04 Thread sebb
Have a look at the scripts in

http://svn.apache.org/viewvc/commons/scripts/

I used those for VALIDATOR and NET.

On 4 May 2016 at 04:43, Josh Elser  wrote:
> Here's what I've been doing. The generic instructions are woefully
> incomplete (before someone chimes in again - no, not just because "VFS is a
> multi-module project"). I think I have this on point for rc1, so I'm writing
> it down here before I forget (we can figure out where it *should* go later).
>
> rc0 only:
> # Make the branch
> $ svn cp trunk branches/VFS-XXX
> $ cd branches/VFS-XXX
> # Set the proper versions
> $ mvn release:prepare

We use a tag not a branch, but perhaps that is what the release plugin does.
In which case I assume the branch is taken to avoid mangling trunk?

> ---
>
> # Or just set it to your JDK6 installation -- this works on OSX
> $ export JAVA_HOME=$(/usr/libexec/java_home -v1.6)
>
> # Where ${asf.username} for me is "elserj"
> $ mvn clean package -Duser.name=${asf.username}

No need to use package if using CP40

> # Set back to 1.7 because my 1.6 installation has trouble deploying to nexus
> $ export JAVA_HOME=$(/usr/libexec/java_home -v1.7)

So does mine; in which case use -Pjava-1.6 below.

> $ mvn deploy -Prelease -Duser.name=${asf.username}
>
> # This is what could be consolidated via one invocation of `mvn site`
> $ mvn site:site site:stage
>
> # Move back to the root SVN repo
> $ cd ../..
> $ svn cp branches/VFS-XXX tags/commons-vfs-project-XXX-rcN

Isn't that what the release plugin does?

You might find

http://svn.apache.org/viewvc/commons/scripts/create_RC_tag.sh

easier to use - it does it all for you without needing to create a
temporary branch.

> --
>
> Things not covered above:
>
> * Copying artifacts (tarballs/zips, xsums, and sigs) into
> dist.a.o/dev/commons/... (building md5/sha1 files)
> * Closing staging repo in Nexus

That can be done using Nexus2DistDev.sh

> --
>
> Some things that could still be improved that I didn't fix:
>
> * Artifacts in dist/target are renamed when they're installed/deployed, but
> not in the local directory. Should do a rename of the file on disk so that
> what is on the RM's computer matches what is in their m2 repo and ASF nexus.

Or ignore the local copies and use Nexus2DistDev.sh which copies the
bin/src artifacts from Nexus and deploys to dist/dev and can remove
them from Nexus before closing the staging repo.

AFAIK only the deploy directory (i.e. Nexus) has the hashes.

> * `mvn site` which invokes site:site and site:stage automatically (which
> would make for a more natural build process -- `mvn deploy` would build the
> site automatically)

I don't follow that.

> Again, for now, this is just for my benefit. When this is all over, I'll try
> to add this all to the website. Please point out anything wrong/missing.
> Thanks.
>
> - Josh
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

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



Re: [VOTE] Apache Commons VFS 2.1 rc1

2016-05-04 Thread Jörg Schaible
Hi Stian,

Stian Soiland-Reyes wrote:


[snip]

> -1 Unclassified use of encryption libraries Bouncy Castle/Apache
> Mina/SSHD/Hadoop/jsch/Jetty (plus some AES128 in DefaultCryptor) - but
> Commons VFS is not classified on
> http://www.apache.org/licenses/exports/


Sorry, but I fail to see the problem. BC is used as test dependency only and 
it is nowhere part of our deliveries or used in our code. AES128 is part of 
the Java runtime.

Cheers,
Jörg


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



Re: [math]: [MATH-1330] - KMeans clustering algorithm, doesn't support clustering of sparse input data.

2016-05-04 Thread Gilles

Hello.

On Sun, 1 May 2016 02:57:59 +0300, Artem Barger wrote:

​Hi,​


On Sun, May 1, 2016 at 12:25 AM, Gilles 


wrote:

Therefore I started to wonder why not to use RealVector


instead, since it has sparse implementation so I will be able to 
leverage

it.



The principle is fine; but I'm wary to use "RealVector" in new code
since it must be refactored...



​By refactoring, do you mean MATH-765​?


Yes.





Right now using kmeans++ clustering algorithm provided by 
common.maths
it's not doable to cluster entire wikipedia dataset or any other 
huge

datasets.



Could you expand on this application?  What is the data?


​The data is tf-idf matrix of wikipedia data set produced by gensim. 
I'm

trying to run coreset algorithm with Spark streaming
and I need kmeans++ for local computation.​




[One of the things to bear in mind while testing new implementations
is to not loose performance on the other classes of problems (or 
you'll

take heat from some of this list's observers...).]



​Is there any performance tests or regression, so it could be used to
validate whenever new implementation doesn't introduced
significant regression?


Not really.

There is a class "PertTestUtils" (in the "test" part of the source code
repository) that could compare execution time between alternative
implementations of some functionality.
I think that it's reliable enough to detect significant performance 
issues.


Otherwise, there is the (now "standard"?) JMH benchmarking tool.

Regards,
Gilles




On Sat, Apr 30, 2016 at 11:41 PM, Gilles 


wrote:

On Mon, 25 Apr 2016 15:52:03 +0300, Artem Barger wrote:


Hi All,


I'd like to provide a solution for [MATH-1330] issue. Before 
starting I

have a concerns regarding the possible design and the actual
implementation.

Currently all implementations of Clusterer interface expect to 
receive
instance of DistanceMeasure class, which used to compute distance 
or

metric
between two points. Switching clustering algorithms to work with 
Vectors
will make this unnecessary, therefore there will be no need to 
provide
DistanceMeasure, since Vector class already provides methods to 
compute

vector norms.


I think that reasons for using "double[]" in the 
"o.a.c.m.ml.clustering"

package were:
 * simple and straightforward (fixed dimension Cartesian 
coordinates)
 * not couple it with the "o.a.c.m.linear" package whose 
"RealVector" is
   for variable size sequences of elements (and is also, 
inconsistently,
   used as a Cartesian vector, and also as column- and 
row-matrix[1])


It is arguable adapted for a family of problems which the 
developer

probably had in mind when taking those design decisions.

It would be interesting to know for which class of problems, the 
design

is inappropriate, in order to clarify ideas.

The main drawback of this approach is that we will loose the 
ability to


control which metric to use during clustering, however the only 
classes

which make an implicit use of this parameters are: Clusterer and
KmeansPlusPlusClusterer all others assumes EucledianDistance by 
default.




There is a default indeed, but all "Clusterer" implementations use
whatever "DistanceMeasure" has been passed to the constructor.

Assuming that "RealVector" knows how to compute the distance means 
that
users will have to implement their own subclass of "RealVector" 
and

override "getDistance(RealVector)" if they want another distance.
Alternatively, CM would have to define all these classes.

At first sight, it does not seem the right way to go...

One of the possible approaches is to extend DistanceMeasure 
interface to

be

able to compute distance between two vectors? After all it's only 
sub

first
vector from the second and compute desired norm on the result.



Seems good (at first sight) but (IMHO) only if we implement a new
"CartesianVector" class unencumbered with all the cruft of 
"RealVector".


Another possible solution is to make vector to return it's 
coordinates,


hence it avail us to use DistanceMeasure as is. Personally I do 
not

think
this is good approach, since it will make no sense with sparse 
vectors.




Ruled out indeed if it conflicts with your intended usage.

Last alternative this comes to my mind is to create a set of enums 
to


indicate which vector norm to use to compute distances, also do 
no think
this is very good solution, since sounds too intrusive and might 
break

backward compatibility.


And forward compatibility (clustering code will have to be adapted 
if

another distance is added later).

What do you think? Am I missing something? Is there a better 
possible way



to achieve the goal?


As indicated above, a practical example might help visualize the 
options.



Regards,
Gilles

[1] Cf. https://issues.apache.org/jira/browse/MATH-765


Best regards,

  Artem Barger.



-
To 

Re: [VFS] Disallowed dependencies in build? (was Re: [VOTE] Apache Commons-VFS2 2.1 rc0)

2016-05-04 Thread Josh Elser

Bernd Eckenfels wrote:

Am Tue, 03 May 2016 21:47:43 -0400
schrieb Josh Elser:


See the original point of me starting this thread: it was stated that
the sandbox (might) depend on code which is not licensed in such a
manner that is allowed for ASF projects.


Which is why it is not built or shipped by default and called sandbox.
(this was not my idea and before my time but I dont see a reason to
change this for this release)

Gruss
Bernd

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



I was just pointed to http://www.apache.org/legal/resolved.html#optional

The way this reads, because we don't push it to Nexus, that's fine.

The other half is that I was (incorrectly) assuming that the src release 
was still including the sandbox. This is wrong -- there are no 
occurrences of it in release artifacts.


I'm good now :)

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



US Export classification & ECCN registration for encryption in commons?

2016-05-04 Thread Stian Soiland-Reyes
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 VFS depends on Bouncy Castle/Apache
Mina/Jetty/SSHD/Hadoop/jsch and has encryption binding for AES128 -
perhaps that also needs to be listed and registered?


We only have listed:

Commons Compress
Commons OpenPGP


See guidance on
http://www.apache.org/dev/crypto.html


BTW - I've raised https://issues.apache.org/jira/browse/LEGAL-250 to
see if merely using a listed source as a Maven  means you
also are classified - or if you would need to also bundle the
dependency's binary (which I think we don't do).



-- 
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/-0001-9842-9718

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



Re: [VOTE] Apache Commons VFS 2.1 rc1

2016-05-04 Thread Stian Soiland-Reyes
+1 (non-binding)

+1 signatures
+1 hashes
+1 LICENSE, NOTICE
0 README.md says 2.0
0 Extra README.txt (confusing)
+1 RELEASE-NOTES.txt
+1 mvn apache-rat:check
+1 maven repository signatures/hashes
+1 maven repository *distribution* matches dist/
0 mvn clean install OK (but 1 test fails on tmpfs)
+1 target/*jar matches binaries
+1 source matches svn tag (minus sandbox/ :-) )
+1 Dependency licenses OK
-1 Unclassified use of encryption libraries Bouncy Castle/Apache
Mina/SSHD/Hadoop/jsch/Jetty (plus some AES128 in DefaultCryptor) - but
Commons VFS is not classified on
http://www.apache.org/licenses/exports/

I won't take a stand on the US Export classification requirement as
https://issues.apache.org/jira/browse/LEGAL-250 has not been resolved
yet.


I get this test error (because my /tmp is mounted with noexec):

Tests run: 90, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.259
sec <<< FAILURE! - in
org.apache.commons.vfs2.provider.local.test.LocalProviderTestCase
testExecutable(org.apache.commons.vfs2.test.PermissionsTests)  Time
elapsed: 0.011 sec  <<< FAILURE!
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at 
org.apache.commons.vfs2.test.PermissionsTests.testExecutable(PermissionsTests.java:70)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.commons.vfs2.test.AbstractProviderTestCase.runTest(AbstractProviderTestCase.java:218)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:252)
at junit.framework.TestSuite.run(TestSuite.java:247)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:23)
at 
org.apache.commons.vfs2.test.AbstractTestSuite$1.protect(AbstractTestSuite.java:149)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at 
org.apache.commons.vfs2.test.AbstractTestSuite.run(AbstractTestSuite.java:154)

Building from /var/tmp worked.

I won't fail because of this - I'm probably special still using tmpfs
:)   (And adding conditional testing would mean using the same APIs or
requivalent Java 7 NIO files APIs to see if executable bit is
supported).


Checked with:

stain@biggie:/tmp/vfs/source/commons-vfs-2.1$ mvn -v
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T16:41:47+00:00)
Maven home: /home/stain/software/maven
Java version: 1.8.0_72-internal, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "3.16.0-67-generic", arch: "amd64", family: "unix"

On 4 May 2016 at 04:43, Josh Elser  wrote:
> All,
>
> Please consider the following for Apache Commons VFS2 version 2.1 (rc1).
>
> Maven repository:
> https://repository.apache.org/content/repositories/orgapachecommons-1163
> Artifacts: https://dist.apache.org/repos/dist/dev/commons/vfs/ r13511
>
> MD5  commons-vfs-distribution-2.1-bin.tar.gz
> 1192914d1ba6f8ca3a2a688feeff602c
> SHA1 commons-vfs-distribution-2.1-bin.tar.gz
> 285097f1db6cbc9d76ae5bb3adf66a315344a864
> MD5  commons-vfs-distribution-2.1-src.tar.gz
> 0646187562302a7dcfbddb93204fc9eb
> SHA1 commons-vfs-distribution-2.1-src.tar.gz
> 24bab87fd4049b9389acd1b6e272f405630aeb25
> MD5  commons-vfs-distribution-2.1-bin.zip 3785874aa0cda64d68acbb8fb7db8bea
> SHA1 commons-vfs-distribution-2.1-bin.zip
> 942a23fb202b89b1a8432beeb0a66469959e661d
> MD5  commons-vfs-distribution-2.1-src.zip c8ef43d308bed1b3ffcb363c15285176
> SHA1 commons-vfs-distribution-2.1-src.zip
> 1ddf0d218f659766f136894eab0beca504ab9f8c
>
> Signed with 4677D66C from
> https://dist.apache.org/repos/dist/release/commons/KEYS
>
> SVN tag is available at
> https://svn.apache.org/repos/asf/commons/proper/vfs/tags/commons-vfs-project-2.1-RC1/
> r1742212
>
> Staged Maven website:
> http://home.apache.org/~elserj/commons/commons-vfs-2.1/
>
> All reports are available in the provided staged Maven site (see "Project
> Reports" at the root-level as well as under each sub-module). JIRA-generated
> release notes are available in the dist.a.o "Artifacts" repository. Unit
> tests pass and the RC was built util JDK6.
>
> (For Sebb) A direct Clirr link
> http://home.apache.org/~elserj/commons/commons-vfs-2.1/commons-vfs2/clirr-report.html
>
> Changes since rc0:
>
> * Improved release notes and website for compatibility
> * Fixes to pom.xml for building website
>
> 

Re: [CRYPTO] How to build CRYPTO on Mac OS 10.11?

2016-05-04 Thread Benedikt Ritter
Thank you Dapeng! I'll give it a try later today.

Sun, Dapeng  schrieb am Mi., 4. Mai 2016 um 05:33 Uhr:

> Hi Benedikt,
>
> Hope this information will be helpful
>
> 1. Upgrade openssl to 1.0.1c above using brew(http://brew.sh/)[1]:
> Check your openssl version, by default it's not 1.0.1
> $openssl version
> OpenSSL 0.9.8r 8 Feb 2011
>
> $ brew search openssl
> $ brew install homebrew/versions/openssl101
> $ brew link openssl --force
>
> Open a new terminal window, test your openssl version, it should be 1.0.1
> now
> $ openssl version
> OpenSSL 1.0.1s 1 Mar 2016
> If not, please check if Homebrew /usr/local/bin if at the front of $PATH
>
> 2. Download and install JCE Unlimited Strength Jurisdiction Policy Files[2]
>
> Download the Java Cryptography Extension (JCE) Unlimited Strength
> Jurisdiction Policy Files from Oracle.
> For JDK 1.6:
> http://www.oracle.com/technetwork/java/javase/downloads/jce-6-download-429243.html
> For JDK 1.7:
> http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html
> For JDK 1.8:
> http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html
>
> Uncompress and extract the downloaded file. The download includes a
> Readme.txt and two .jar files with the same names as the existing policy
> files.
>
> Replace local_policy.jar and US_export_policy.jar at
> /lib/security/
>
> 3. Set system environment JAVA_HOME[3]
> $ echo $JAVA_HOME
> In Mac OSX 10.5 or later, Apple recommends to set the $JAVA_HOME variable
> to /usr/libexec/java_home, just export $JAVA_HOME in file ~/. bash_profile
> or ~/.profile.
>
> I have tried it on local machine, please feel free to let me know if you
> still have any problem.
>
> Regards
> Dapeng
>
> [1]
> http://stackoverflow.com/questions/15185661/update-openssl-on-os-x-with-homebrew
> [2]
> https://www.attachmate.com/documentation/rweb/rweb-installguide/data/b1gdutii.htm
> [3]
> http://www.mkyong.com/java/how-to-set-java_home-environment-variable-on-mac-os-x/
>
> -Original Message-
> From: Benedikt Ritter [mailto:brit...@apache.org]
> Sent: Wednesday, May 04, 2016 12:39 AM
> To: Commons Developers List
> Subject: Re: [CRYPTO] How to build CRYPTO on Mac OS 10.11?
>
> Chen, Haifeng  schrieb am Di., 3. Mai 2016 um
> 03:49 Uhr:
>
> > Sorry to not response in the past days due to Holiday here.
> > We will start to check that. I agree that JNA is a good thing to try
> > as long as the performance impact is in an acceptable level.
> >
>
> It would be good enough for me to have some documentation on how to setup
> the development environment. If none of the crypto developers uses Mac OS,
> I'll need to figure out and document myself. Maybe somebody can help me via
> hang out to understand better what the requirements are.
>
> Regards,
> Benedikt
>
>
> >
> >
> > -Original Message-
> > From: sebb [mailto:seb...@gmail.com]
> > Sent: Monday, May 2, 2016 6:51 PM
> > To: Commons Developers List 
> > Subject: Re: [CRYPTO] How to build CRYPTO on Mac OS 10.11?
> >
> > On 2 May 2016 at 11:45, Benedikt Ritter  wrote:
> > > sebb  schrieb am So., 1. Mai 2016 um 21:19 Uhr:
> > >
> > >> On 1 May 2016 at 19:17, Benedikt Ritter  wrote:
> > >> > Hi,
> > >> >
> > >> > today I started working on the site build. I ran into problems
> > >> > with the native build and with different JDK versions. Can anybody
> help?
> > >> > I've documented my problems in CRYPTO-45 [1].
> > >>
> > >> I think you have discovered why there were concerns about using JNI...
> > >>
> > >
> > > :-)
> > >
> > > I think it just has to be documented. The problem seems to be
> > > specific to Mac OS 10.11.
> >
> > But it's not possible to document these problems without having access
> > to the relevant OS.
> >
> > And even if one does, this is a non-trivial exercise as you have just
> > shown.
> >
> > >
> > >>
> > >> > Regards,
> > >> > Benedikt
> > >> >
> > >> > [1] https://issues.apache.org/jira/browse/CRYPTO-45
> > >>
> > >> ---
> > >> -- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > >> For additional commands, e-mail: dev-h...@commons.apache.org
> > >>
> > >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>


Re: [VFS] Disallowed dependencies in build? (was Re: [VOTE] Apache Commons-VFS2 2.1 rc0)

2016-05-04 Thread Bernd Eckenfels
Am Tue, 03 May 2016 21:47:43 -0400
schrieb Josh Elser :

> See the original point of me starting this thread: it was stated that 
> the sandbox (might) depend on code which is not licensed in such a 
> manner that is allowed for ASF projects.

Which is why it is not built or shipped by default and called sandbox.
(this was not my idea and before my time but I dont see a reason to
change this for this release)

Gruss
Bernd

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