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

2016-05-02 Thread Chen, Haifeng
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. -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Monday, May 2, 2016 6:51 PM To:

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Gary Gregory
Yeah, I do not think we want to release the sandbox because it will drag in jar(s) that have a license that is not ASL 2 friendly IIRC. Gary On Mon, May 2, 2016 at 5:36 PM, wrote: > Hello, > > Agree, the sandbox profile should be in the site build enabled, but we >

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

2016-05-02 Thread Josh Elser
Binaries are not an official release anyways. Even so, that seems like a *very* scary thing to even have this code checked into the repository if it depends on incompatibly-licensed software. Am I misunderstanding this? e...@zusammenkunft.net wrote: Hello, Agree, the sandbox profile should

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Josh Elser
Josh Elser wrote: sebb wrote: On 2 May 2016 at 15:00, Josh Elser wrote: > Also, please re-read the end of the previous thread on compatibility. > > I clearly stated that there were some changes which I consider not worth > changing about the TarArchiveEntry code. If you feel

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread ecki
Hello, Agree, the sandbox profile should be in the site build enabled, but we cannot distribute the binaries as official release since it has dependencies which are not Apache approved (and potentially unfinished suff). Gruss Bernd -- http://bernd.eckenfels.net -Original Message-

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Josh Elser
I had just tried to make sure it was included in the build because I assumed that it was meant to be released :) It's becoming apparent that was inaccurate. Ralph Goers wrote: As I recall 2.0 did not really include sandbox as part of the release because we didn’t want to officially support

Re: [VFS] JIRA Karma?

2016-05-02 Thread Josh Elser
Thanks Benedikt! Benedikt Ritter wrote: Hello Josh, Josh Elser schrieb am So., 1. Mai 2016 um 21:46 Uhr: Can someone grant me some karma on the VFS project, please? I'll eventually need to some version management, but, even now, it seems like I can't assign an issue to

Re: [VOTE] Commons NET 3.5 based on RC3

2016-05-02 Thread Jörg Schaible
Hi, builds fin from source wiht my ocmplete coimpiler zoo ... except Java 9, but not because of failing tests - it's the jar plugin that fails in the package phase ;-) %< == Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;

Re: [VOTE] Commons NET 3.5 based on RC3

2016-05-02 Thread Benedikt Ritter
Hello sebb, Tested with: - Java 6 and Maven 3.2.5 - Java 7 and 8 and Maven 3.3.9 sebb schrieb am Mo., 2. Mai 2016 um 01:12 Uhr: > Try again. > > == > > NET 3.5 RC3 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/net/3.5_RC3/ (13489) > >

Re: [VFS] JIRA Karma?

2016-05-02 Thread Benedikt Ritter
Hello Josh, Josh Elser schrieb am So., 1. Mai 2016 um 21:46 Uhr: > Can someone grant me some karma on the VFS project, please? I'll > eventually need to some version management, but, even now, it seems like > I can't assign an issue to myself. > I've added you to the

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Ralph Goers
As I recall 2.0 did not really include sandbox as part of the release because we didn’t want to officially support the sandbox components. They might have been included in the source distribution though. But these emails make it sound like it is exactly the opposite of what I would have

Re: [VOTE] Commons NET 3.5 based on RC3

2016-05-02 Thread Oliver Heger
Build works fine with Java 1.6 and 1.8 on Windows 10. Artifacts and site look good. +1 Oliver Am 02.05.2016 um 01:12 schrieb sebb: > Try again. > > == > > NET 3.5 RC3 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/net/3.5_RC3/ (13489) > >

Re: [VFS] JIRA Karma?

2016-05-02 Thread Gary Gregory
On Mon, May 2, 2016 at 11:47 AM, sebb wrote: > On 2 May 2016 at 19:29, Gary Gregory wrote: > > Josh, > > > > For now, tell us what you need and one of us will fiddle. > > Be careful when adjusting JIRA permissions. > We don't want a repeat of the recent

Re: [Math] About MATH-667 (Complex numbers)

2016-05-02 Thread Eric Barnhill
Reading over the discussion, there were some contrasting views about which of the common complex number behaviors Complex() ought to emulate. One commentator suggested GNU Octave. My quick take is that Octave has some good momentum right now, with its new editor and it's GSOC presence, and

Re: [VFS] JIRA Karma?

2016-05-02 Thread sebb
On 2 May 2016 at 19:29, Gary Gregory wrote: > Josh, > > For now, tell us what you need and one of us will fiddle. Be careful when adjusting JIRA permissions. We don't want a repeat of the recent spams. > Gary > > On Mon, May 2, 2016 at 11:29 AM, Gary Gregory

Re: [VFS] JIRA Karma?

2016-05-02 Thread Gary Gregory
Josh, For now, tell us what you need and one of us will fiddle. Gary On Mon, May 2, 2016 at 11:29 AM, Gary Gregory wrote: > On the admin page I see: > > >- Project Permissions > > _Default Permission Scheme_SHARED BY 53 PROJECTS >

Re: [VFS] JIRA Karma?

2016-05-02 Thread Gary Gregory
On the admin page I see: - Project Permissions _Default Permission Scheme_SHARED BY 53 PROJECTS So do not have a custom set up for VFS or any Commons component I would guess.

Re: [VFS] JIRA Karma?

2016-05-02 Thread Matt Sicker
That would make sense considering any committer can commit. On 2 May 2016 at 13:25, Gary Gregory wrote: > I created a 3.0 version just for fun... but... it seems that while we > opened up Commons to all Apache Committers, JIRA is another matter. > > To assign an issue,

Re: [VFS] JIRA Karma?

2016-05-02 Thread Gary Gregory
I created a 3.0 version just for fun... but... it seems that while we opened up Commons to all Apache Committers, JIRA is another matter. To assign an issue, you must be one of: - Project Role (PMC) - Project Role (Committers) - Project Role (Administrators) - Group

Re: [VOTE] Commons NET 3.5 based on RC3

2016-05-02 Thread Gary Gregory
+1, >From src-zip, MD5, SHA1, ASC OK. Builds mvn clean site OK with: 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.8.0_91, vendor: Oracle Corporation Java home: C:\Program

Re: [VOTE] Commons NET 3.5 based on RC3

2016-05-02 Thread Stian Soiland-Reyes
+1 (non-binding) +1 signatures, hashes +1 tar vs gz +1 src has no binaries (except logo) 0 README.md OK (except it says 3.5-SNAPSHOT) +1 RELEASE-NOTES.txt +1 mvn clean install stain@biggie:/tmp/3.5_RC3/src/commons-net-3.5-src$ mvn -v Apache Maven 3.3.9

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Josh Elser
sebb wrote: http://home.apache.org/~elserj/commons/commons-vfs-2.1/index.html mentions Release Notes but the link points to https://archive.apache.org/dist/commons/vfs/RELEASE_NOTES.txt which of course is for2.0. It would be helpful to use the current release notes on the site. Ok, I'll

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Josh Elser
sebb wrote: On 2 May 2016 at 15:00, Josh Elser wrote: > Also, please re-read the end of the previous thread on compatibility. > > I clearly stated that there were some changes which I consider not worth > changing about the TarArchiveEntry code. If you feel like these are

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread sebb
On 2 May 2016 at 15:00, Josh Elser wrote: > Also, please re-read the end of the previous thread on compatibility. > > I clearly stated that there were some changes which I consider not worth > changing about the TarArchiveEntry code. If you feel like these are not > acceptable,

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread sebb
http://home.apache.org/~elserj/commons/commons-vfs-2.1/index.html mentions Release Notes but the link points to https://archive.apache.org/dist/commons/vfs/RELEASE_NOTES.txt which of course is for 2.0. It would be helpful to use the current release notes on the site. The new RN at

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Josh Elser
Also, please re-read the end of the previous thread on compatibility. I clearly stated that there were some changes which I consider not worth changing about the TarArchiveEntry code. If you feel like these are not acceptable, please start a discussion about this so you can come to consensus

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Josh Elser
sebb wrote: The "Download and Build" page is more suitable for developers than end users (especially if it points to trunk, which is not voted on) so should not be the primary download page. Also there seem to be two identical copies of each of the non-Maven release artifacts:

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Josh Elser
Josh Elser wrote: Sebb wrote: > Please consider the following for Apache Commons VFS2 version 2.1 (rc0). > > Maven repository: > https://repository.apache.org/content/repositories/orgapachecommons-1161 The e-mail should contain the hashes of the release items as the above URL is transitory.

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Josh Elser
(So sorry, fingers sent too quick) commons-vfs-2.1-bin.tar.gz: MD5 fdaad280f3d3c592df048a58bfa8debd SHA1 edfa8ac8c31e2e4b88898ac2418f9e7a7fe34324 commons-vfs-2.1-bin.zip: MD5 951448d632ff37363c4bd0dcad3a887e SHA1 2fd9262d349f6d62eb34912a7d56d406b7655568 My GPG key is 4677D66C Josh Elser

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Josh Elser
Forgot to include xsum/sig info: commons-vfs-2.1-src.tar.gz: MD5 f768cf5f2d00cfa58b70d221054ca1c9 SHA1 d5a53ecf575e961b2e6b472e8bf5b013b33bfa78 commons-vfs-2.1-src.zip: MD5 2eb6a10883b77ce137a391a7dd341120 SHA1 f831eb7cb62df295ef8b1a090e209550c6ea5c35 Josh Elser wrote: All, Please consider

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Josh Elser
Hrm, so I either botched the build command (highly possible) or the source archive is screwed up and doesn't include it. Can someone please enlighten me as to whether or not the sandbox should actually be included? sebb wrote: Also the sandbox tree is missing from the source archives. Yet

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Josh Elser
Sebb -- did you actually read the changes? You should note that those are all method additions which we already decided were allowed sebb wrote: I have now found the Clirr Report at http://home.apache.org/~elserj/commons/commons-vfs-2.1/commons-vfs2/clirr-report.html There are still some

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread Josh Elser
Sebb wrote: > Please consider the following for Apache Commons VFS2 version 2.1 (rc0). > > Maven repository: > https://repository.apache.org/content/repositories/orgapachecommons-1161 The e-mail should contain the hashes of the release items as the above URL is transitory. The hashes allow

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread sebb
I have now found the Clirr Report at http://home.apache.org/~elserj/commons/commons-vfs-2.1/commons-vfs2/clirr-report.html There are still some breaking changes that affect BC as far as I can tell, so that means I need to vote -1 On 2 May 2016 at 11:31, sebb wrote: > Also

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

2016-05-02 Thread sebb
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

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

2016-05-02 Thread Benedikt Ritter
Gary Gregory schrieb am So., 1. Mai 2016 um 22:27 Uhr: > On May 1, 2016 12:19 PM, "sebb" wrote: > > > > On 1 May 2016 at 19:17, Benedikt Ritter wrote: > > > Hi, > > > > > > today I started working on the site build. I ran into

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

2016-05-02 Thread Benedikt Ritter
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

Re: [LANG] Failing tests

2016-05-02 Thread Benedikt Ritter
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 Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home/jre Default

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread sebb
Also the sandbox tree is missing from the source archives. Yet there are sandbox jars in Nexus. We cannot publish source to Maven that is not also in the source artifacts. If the sandbox code is not intended to be released, it should be moved from trunk. On 2 May 2016 at 11:16, sebb

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread sebb
Also please include a link to the KEYS file, i.e. https://www.apache.org/dist/commons/KEYS Note that the standard download page is http://home.apache.org/~elserj/commons/commons-vfs-2.1/download_vfs.html I think that should be in the site menu. The "Download and Build" page is more suitable

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

2016-05-02 Thread sebb
On 2 May 2016 at 05:28, Josh Elser wrote: > All, > > Please consider the following for Apache Commons VFS2 version 2.1 (rc0). > > Maven repository: > https://repository.apache.org/content/repositories/orgapachecommons-1161 The e-mail should contain the hashes of the release

Build failed in Jenkins: Commons-CRYPTO #24

2016-05-02 Thread Apache Jenkins Server
See -- Started by user sdp [EnvInject] - Loading node environment variables. Building remotely on ubuntu3 (Ubuntu ubuntu legacy-ubuntu) in workspace >

Re: [LANG] Failing tests

2016-05-02 Thread Chas Honton
The line number makes it look like the Parameterized values are not being properly set by junit. Is it possible that we're using a new parent Pom that doesn't fully configure junit plugin version? What version of maven are you using? I just successfully built from tip on a Mac using maven