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

[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: 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: [VOTE] Apache Commons-VFS2 2.1 rc0

[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
> 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-
> From: Josh Elser 
> To: Commons Developers List 
> Sent: Di., 03 Mai 2016 2:33
> Subject: Re: [VOTE] Apache Commons-VFS2 2.1 rc0
>
> 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 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
> expected.
> >
> > Ralph
> >
> >> On May 2, 2016, at 6:35 AM, Josh Elser  wrote:
> >>
> >> 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:
> >>> commons-vfs-2.1-bin
> >>> and
> >>> commons-vfs2-distribution-2.1-bin
> >>>
> >>> etc.
> >>>
> >>>
> >>> Are they supposed to be the same? If not what is missing from one of
> them?
> >> I have no idea. This is just what your build process did...
> >>
> >> -
> >> 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
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

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

[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 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



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

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

[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 like these are
not
> acceptable, please start a discussion about this so you can come to
> consensus on how the changes should be addressed.


The release vote mail really needs to include all the release-specific
information that the reviewer needs to do the review.

If there are caveats etc relating to the Clirr report these need to be
included in the vote mail.
Both to make it easier for the reviewers, and for the historical
record to show that these items were considered.



Ok, this was not made clear to me. Thank you for letting me know. I'd
encourage you to update your project's website. For other projects, I
assume that those voting would have the context from previous
discussions, but acknowledge that this is not how commons operates.


Sebb -- would addressing these points in the release notes cause you to 
change your -1 to a +1? I'd like to make all the changes I can ASAP and 
roll the next RC. Because I haven't said it explicitly -- thanks for 
taking the time to give all of the feedback that you have already.


Everyone else -- even though Sebb voted -1 on rc0, I would greatly 
appreciate if everyone could still look through rc0 and give any more 
feedback which would keep you from a +1.


Thanks.

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

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

[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-
From: Josh Elser 
To: Commons Developers List 
Sent: Di., 03 Mai 2016 2:33
Subject: Re: [VOTE] Apache Commons-VFS2 2.1 rc0

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 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 expected.
>
> Ralph
>
>> On May 2, 2016, at 6:35 AM, Josh Elser  wrote:
>>
>> 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:
>>> commons-vfs-2.1-bin
>>> and
>>> commons-vfs2-distribution-2.1-bin
>>>
>>> etc.
>>>
>>>
>>> Are they supposed to be the same? If not what is missing from one of them?
>> I have no idea. This is just what your build process did...
>>
>> -
>> 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


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

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

[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 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 expected.

Ralph


On May 2, 2016, at 6:35 AM, Josh Elser  wrote:

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:
commons-vfs-2.1-bin
and
commons-vfs2-distribution-2.1-bin

etc.


Are they supposed to be the same? If not what is missing from one of them?

I have no idea. This is just what your build process did...

-
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: [VFS] JIRA Karma?

[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 myself.



I've added you to the commons-developers group. You should now be able to
assign and modify issues.

Benedikt



Thanks in advance.

- 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] Commons NET 3.5 based on RC3

[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; 
2015-11-10T17:41:47+01:00)
Maven home: /usr/share/maven-bin-3.3
Java version: 9-ea, vendor: Oracle Corporation
Java home: /opt/oracle-jdk-bin-1.9.0.0_beta116
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.6-gentoo", arch: "amd64", family: "unix"
 %< ==

So +1

Cheers,
Jörg

sebb wrote:

> 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] Commons NET 3.5 based on RC3

[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)
>
> 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
>
>
>   [ x ] +1 Release these artifacts
>

Thank you,
Benedikt


>   [ ] +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: [VFS] JIRA Karma?

[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 commons-developers group. You should now be able to
assign and modify issues.

Benedikt


>
> Thanks in advance.
>
> - Josh
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

[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 expected.

Ralph

> On May 2, 2016, at 6:35 AM, Josh Elser  wrote:
> 
> 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:
>> commons-vfs-2.1-bin
>> and
>> commons-vfs2-distribution-2.1-bin
>> 
>> etc.
>> 
>> 
>> Are they supposed to be the same? If not what is missing from one of them?
> 
> I have no idea. This is just what your build process did...
> 
> -
> 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] Commons NET 3.5 based on RC3

[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)
> 
> 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
> 

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

Re: [VFS] JIRA Karma?

[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 spams.
>

I was not planning on doing any JIRA admin, just assigning issues and such.

Gary


> > 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
> >> <
> https://issues.apache.org/jira/plugins/servlet/project-config/VFS/permissions#project-config-permissions-0-shared
> >
> >>
> >> So do not have a custom set up for VFS or any Commons component I would
> >> guess.
> >>
> >> We do not have 53 components in Commons IIRC.
> >>
> >> So we'd need to clone this config and then go from there. More than I
> can
> >> handle today! And this might be an INFRA thing...
> >>
> >> Gary
> >>
> >> On Mon, May 2, 2016 at 11:26 AM, Matt Sicker  wrote:
> >>
> >>> 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, you must be one of:
> >>> >
> >>> >
> >>> >- Project Role (PMC)
> >>> >- Project Role (Committers)
> >>> >- Project Role (Administrators)
> >>> >- Group (jira-administrators)
> >>> >
> >>> > Should we make it such that any Apache Committer can assign an issue?
> >>> >
> >>> > Gary
> >>> >
> >>> >
> >>> > On Sun, May 1, 2016 at 12:46 PM, Josh Elser 
> wrote:
> >>> >
> >>> > > 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.
> >>> > >
> >>> > > Thanks in advance.
> >>> > >
> >>> > > - Josh
> >>> > >
> >>> > >
> -
> >>> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >>> > > For additional commands, e-mail: dev-h...@commons.apache.org
> >>> > >
> >>> > >
> >>> >
> >>> >
> >>> > --
> >>> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> >>> > Java Persistence with Hibernate, Second Edition
> >>> > 
> >>> > JUnit in Action, Second Edition 
> >>> > Spring Batch in Action 
> >>> > Blog: http://garygregory.wordpress.com
> >>> > Home: http://garygregory.com/
> >>> > Tweet! http://twitter.com/GaryGregory
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>> Matt Sicker 
> >>>
> >>
> >>
> >>
> >> --
> >> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> >> Java Persistence with Hibernate, Second Edition
> >> 
> >> JUnit in Action, Second Edition 
> >> Spring Batch in Action 
> >> Blog: http://garygregory.wordpress.com
> >> Home: http://garygregory.com/
> >> Tweet! http://twitter.com/GaryGregory
> >>
> >
> >
> >
> > --
> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> > Java Persistence with Hibernate, Second Edition
> > 
> > JUnit in Action, Second Edition 
> > Spring Batch in Action 
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

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

[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 that synchronizing Complex() with GNU octave would be a 
good path to take. This would also be a good way for me to get started 
writing some methods that create a smooth bridge between octave and 
commons. Ideally the octave standard is identical with the C99x 
standard, but I don't know yet.


If the group is happy with this, I will also go mention it on 
octave-maintainers and see what I can come up with for a plan.


Eric

On 23/04/16 01:27, Gilles wrote:

Hi.

Branch "feature-MATH-1290" deals with "Complex" utilities.
It is perhaps a good opportunity to review this very old
issue.  And decide whether it is worth keeping it open.

Regards,
Gilles


-
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] JIRA Karma?

[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 
> wrote:
>
>> 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.
>>
>> We do not have 53 components in Commons IIRC.
>>
>> So we'd need to clone this config and then go from there. More than I can
>> handle today! And this might be an INFRA thing...
>>
>> Gary
>>
>> On Mon, May 2, 2016 at 11:26 AM, Matt Sicker  wrote:
>>
>>> 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, you must be one of:
>>> >
>>> >
>>> >- Project Role (PMC)
>>> >- Project Role (Committers)
>>> >- Project Role (Administrators)
>>> >- Group (jira-administrators)
>>> >
>>> > Should we make it such that any Apache Committer can assign an issue?
>>> >
>>> > Gary
>>> >
>>> >
>>> > On Sun, May 1, 2016 at 12:46 PM, Josh Elser  wrote:
>>> >
>>> > > 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.
>>> > >
>>> > > Thanks in advance.
>>> > >
>>> > > - Josh
>>> > >
>>> > > -
>>> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> > > For additional commands, e-mail: dev-h...@commons.apache.org
>>> > >
>>> > >
>>> >
>>> >
>>> > --
>>> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>> > Java Persistence with Hibernate, Second Edition
>>> > 
>>> > JUnit in Action, Second Edition 
>>> > Spring Batch in Action 
>>> > Blog: http://garygregory.wordpress.com
>>> > Home: http://garygregory.com/
>>> > Tweet! http://twitter.com/GaryGregory
>>> >
>>>
>>>
>>>
>>> --
>>> Matt Sicker 
>>>
>>
>>
>>
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> Java Persistence with Hibernate, Second Edition
>> 
>> JUnit in Action, Second Edition 
>> Spring Batch in Action 
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory

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

Re: [VFS] JIRA Karma?

[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
> 
>
> So do not have a custom set up for VFS or any Commons component I would
> guess.
>
> We do not have 53 components in Commons IIRC.
>
> So we'd need to clone this config and then go from there. More than I can
> handle today! And this might be an INFRA thing...
>
> Gary
>
> On Mon, May 2, 2016 at 11:26 AM, Matt Sicker  wrote:
>
>> 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, you must be one of:
>> >
>> >
>> >- Project Role (PMC)
>> >- Project Role (Committers)
>> >- Project Role (Administrators)
>> >- Group (jira-administrators)
>> >
>> > Should we make it such that any Apache Committer can assign an issue?
>> >
>> > Gary
>> >
>> >
>> > On Sun, May 1, 2016 at 12:46 PM, Josh Elser  wrote:
>> >
>> > > 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.
>> > >
>> > > Thanks in advance.
>> > >
>> > > - Josh
>> > >
>> > > -
>> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> > > For additional commands, e-mail: dev-h...@commons.apache.org
>> > >
>> > >
>> >
>> >
>> > --
>> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> > Java Persistence with Hibernate, Second Edition
>> > 
>> > JUnit in Action, Second Edition 
>> > Spring Batch in Action 
>> > Blog: http://garygregory.wordpress.com
>> > Home: http://garygregory.com/
>> > Tweet! http://twitter.com/GaryGregory
>> >
>>
>>
>>
>> --
>> Matt Sicker 
>>
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [VFS] JIRA Karma?

[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.

We do not have 53 components in Commons IIRC.

So we'd need to clone this config and then go from there. More than I can
handle today! And this might be an INFRA thing...

Gary

On Mon, May 2, 2016 at 11:26 AM, Matt Sicker  wrote:

> 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, you must be one of:
> >
> >
> >- Project Role (PMC)
> >- Project Role (Committers)
> >- Project Role (Administrators)
> >- Group (jira-administrators)
> >
> > Should we make it such that any Apache Committer can assign an issue?
> >
> > Gary
> >
> >
> > On Sun, May 1, 2016 at 12:46 PM, Josh Elser  wrote:
> >
> > > 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.
> > >
> > > Thanks in advance.
> > >
> > > - Josh
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > For additional commands, e-mail: dev-h...@commons.apache.org
> > >
> > >
> >
> >
> > --
> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> > Java Persistence with Hibernate, Second Edition
> > 
> > JUnit in Action, Second Edition 
> > Spring Batch in Action 
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
> >
>
>
>
> --
> Matt Sicker 
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [VFS] JIRA Karma?

[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, you must be one of:
>
>
>- Project Role (PMC)
>- Project Role (Committers)
>- Project Role (Administrators)
>- Group (jira-administrators)
>
> Should we make it such that any Apache Committer can assign an issue?
>
> Gary
>
>
> On Sun, May 1, 2016 at 12:46 PM, Josh Elser  wrote:
>
> > 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.
> >
> > Thanks in advance.
> >
> > - Josh
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
Matt Sicker 

Re: [VFS] JIRA Karma?

[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 (jira-administrators)

Should we make it such that any Apache Committer can assign an issue?

Gary


On Sun, May 1, 2016 at 12:46 PM, Josh Elser  wrote:

> 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.
>
> Thanks in advance.
>
> - Josh
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [VOTE] Commons NET 3.5 based on RC3

[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 Files\Java\jdk1.8.0_91\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"

Site reports OK.

Gary

On Sun, May 1, 2016 at 4:12 PM, sebb  wrote:

> 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
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [VOTE] Commons NET 3.5 based on RC3

[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 (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 2 May 2016 at 00:12, sebb  wrote:
> 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
>



-- 
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-VFS2 2.1 rc0

[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 have to figure out how that gets wired up. I have no idea if 
that's dynamic or static.



The new RN at
https://dist.apache.org/repos/dist/dev/commons/vfs/RELEASE-NOTES.txt
don't mention any of the Clirr issues.


Ok, I will update that then.

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

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

[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 not
>  acceptable, please start a discussion about this so you can come to
>  consensus on how the changes should be addressed.


The release vote mail really needs to include all the release-specific
information that the reviewer needs to do the review.

If there are caveats etc relating to the Clirr report these need to be
included in the vote mail.
Both to make it easier for the reviewers, and for the historical
record to show that these items were considered.



Ok, this was not made clear to me. Thank you for letting me know. I'd 
encourage you to update your project's website. For other projects, I 
assume that those voting would have the context from previous 
discussions, but acknowledge that this is not how commons operates.


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

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

[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, please start a discussion about this so you can come to
> consensus on how the changes should be addressed.

The release vote mail really needs to include all the release-specific
information that the reviewer needs to do the review.

If there are caveats etc relating to the Clirr report these need to be
included in the vote mail.
Both to make it easier for the reviewers, and for the historical
record to show that these items were considered.

>
> Josh Elser wrote:
>>
>> 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 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 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 wrote:
>
> 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 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:
> commons-vfs-2.1-bin
> and
> commons-vfs2-distribution-2.1-bin
>
> etc.
>
>
> Are they supposed to be the same? If not what is missing from one of
> them?
>
> On 2 May 2016 at 10:40, sebb wrote:
>>
>> 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 items as the above
>> URL is transitory.
>> The hashes allow one to tie the released files back to the vote
>> thread.
>>
>> They can be copied from the Nexus mail.
>>
>>> Artifacts:
>>> https://dist.apache.org/repos/dist/dev/commons/vfs/{binaries,source}
>>
>> Likewise here we include the revision id of the URL:
>>
>> https://dist.apache.org/repos/dist/dev/commons/vfs/
>>
>>
>>> Staged site:
>>> http://home.apache.org/~elserj/commons/commons-vfs-2.1/index.html
>>
>> There's no Clirr report that I could find.
>>
>> Also the download page links to trunk rather than the specific tag.
>>
>>> All reports are available in the provided staged Maven site.
>>> JIRA-generated
>>> release notes are available in the dist.a.o "Artifacts"
>>> repository. Unit
>>> tests pass and the RC was built util JDK6.
>>
>> E-mail should really have URL to make it easy for reviewers.
>>
>>> The current code is available in branches/VFS-2.1 at r1741921.
>>> This is what
>>> will be copied to tags upon successful passing of this vote.
>>
>> Full URLs in e-mails please.
>> Also it should be a TAG not a branch, as it should be kept if the vote
>> is successful
>>
>>> This vote will be open for 72-hours, 2016/05/05 0500 UTC.
>>>
>>> [ ] +1 Release these artifacts as version 2.1
>>> [ ] 0 OK, but...
>>> [X] -1 I oppose these artifacts as version 2.1 because..
>>
>> As above.
>>
>> No need necessarily to rebuild everything as most of the concerns
>> relate to the vote e-mail and the site.
>> e.g. you can rename the branch as a tag.
>>
>>> - Josh
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: 

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

[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
https://dist.apache.org/repos/dist/dev/commons/vfs/RELEASE-NOTES.txt
don't mention any of the Clirr issues.


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, please start a discussion about this so you can come to
> consensus on how the changes should be addressed.
>
>
> Josh Elser wrote:
>>
>> 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 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 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 wrote:
>
> 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 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:
> commons-vfs-2.1-bin
> and
> commons-vfs2-distribution-2.1-bin
>
> etc.
>
>
> Are they supposed to be the same? If not what is missing from one of
> them?
>
> On 2 May 2016 at 10:40, sebb wrote:
>>
>> 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 items as the above
>> URL is transitory.
>> The hashes allow one to tie the released files back to the vote
>> thread.
>>
>> They can be copied from the Nexus mail.
>>
>>> Artifacts:
>>> https://dist.apache.org/repos/dist/dev/commons/vfs/{binaries,source}
>>
>> Likewise here we include the revision id of the URL:
>>
>> https://dist.apache.org/repos/dist/dev/commons/vfs/
>>
>>
>>> Staged site:
>>> http://home.apache.org/~elserj/commons/commons-vfs-2.1/index.html
>>
>> There's no Clirr report that I could find.
>>
>> Also the download page links to trunk rather than the specific tag.
>>
>>> All reports are available in the provided staged Maven site.
>>> JIRA-generated
>>> release notes are available in the dist.a.o "Artifacts"
>>> repository. Unit
>>> tests pass and the RC was built util JDK6.
>>
>> E-mail should really have URL to make it easy for reviewers.
>>
>>> The current code is available in branches/VFS-2.1 at r1741921.
>>> This is what
>>> will be copied to tags upon successful passing of this vote.
>>
>> Full URLs in e-mails please.
>> Also it should be a TAG not a branch, as it should be kept if the vote
>> is successful
>>
>>> This vote will be open for 72-hours, 2016/05/05 0500 UTC.
>>>
>>> [ ] +1 Release these artifacts as version 2.1
>>> [ ] 0 OK, but...
>>> [X] -1 I oppose these artifacts as version 2.1 because..
>>
>> As above.
>>
>> No need necessarily to rebuild everything as most of the concerns
>> relate to the vote e-mail and the site.
>> e.g. you can rename the branch as a tag.
>>
>>> - Josh
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>
>>> 

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

[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 on how the changes should be addressed.


Josh Elser wrote:

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 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 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 wrote:

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 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:
commons-vfs-2.1-bin
and
commons-vfs2-distribution-2.1-bin

etc.


Are they supposed to be the same? If not what is missing from one of
them?

On 2 May 2016 at 10:40, sebb wrote:

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 items as the above
URL is transitory.
The hashes allow one to tie the released files back to the vote
thread.

They can be copied from the Nexus mail.


Artifacts:
https://dist.apache.org/repos/dist/dev/commons/vfs/{binaries,source}

Likewise here we include the revision id of the URL:

https://dist.apache.org/repos/dist/dev/commons/vfs/



Staged site:
http://home.apache.org/~elserj/commons/commons-vfs-2.1/index.html

There's no Clirr report that I could find.

Also the download page links to trunk rather than the specific tag.


All reports are available in the provided staged Maven site.
JIRA-generated
release notes are available in the dist.a.o "Artifacts"
repository. Unit
tests pass and the RC was built util JDK6.

E-mail should really have URL to make it easy for reviewers.


The current code is available in branches/VFS-2.1 at r1741921.
This is what
will be copied to tags upon successful passing of this vote.

Full URLs in e-mails please.
Also it should be a TAG not a branch, as it should be kept if the vote
is successful


This vote will be open for 72-hours, 2016/05/05 0500 UTC.

[ ] +1 Release these artifacts as version 2.1
[ ] 0 OK, but...
[X] -1 I oppose these artifacts as version 2.1 because..

As above.

No need necessarily to rebuild everything as most of the concerns
relate to the vote e-mail and the site.
e.g. you can rename the branch as a tag.


- 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-VFS2 2.1 rc0

[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:
commons-vfs-2.1-bin
and
commons-vfs2-distribution-2.1-bin

etc.


Are they supposed to be the same? If not what is missing from one of them?


I have no idea. This is just what your build process did...

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

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

[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.
The hashes allow one to tie the released files back to the vote thread.


Ugh, this is what happens when I try to finish this up late at night :)


Also, it's worth nothing that your email template on the website 
(https://commons.apache.org/releases/prepare.html) does not include 
instructions for this which is what I'll blame for forgetting to do this 
on my own.


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

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

[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 wrote:

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 the following for Apache Commons VFS2 version 2.1 (rc0).

Maven repository:
https://repository.apache.org/content/repositories/orgapachecommons-1161

Artifacts:
https://dist.apache.org/repos/dist/dev/commons/vfs/{binaries,source}

Staged site:
http://home.apache.org/~elserj/commons/commons-vfs-2.1/index.html

All reports are available in the provided staged Maven site.
JIRA-generated release notes are available in the dist.a.o "Artifacts"
repository. Unit tests pass and the RC was built util JDK6.

The current code is available in branches/VFS-2.1 at r1741921. This is
what will be copied to tags upon successful passing of this vote.

This vote will be open for 72-hours, 2016/05/05 0500 UTC.

[ ] +1 Release these artifacts as version 2.1
[ ] 0 OK, but...
[ ] -1 I oppose these artifacts as version 2.1 because..

- 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-VFS2 2.1 rc0

[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 the following for Apache Commons VFS2 version 2.1 (rc0).

Maven repository:
https://repository.apache.org/content/repositories/orgapachecommons-1161

Artifacts:
https://dist.apache.org/repos/dist/dev/commons/vfs/{binaries,source}

Staged site:
http://home.apache.org/~elserj/commons/commons-vfs-2.1/index.html

All reports are available in the provided staged Maven site.
JIRA-generated release notes are available in the dist.a.o "Artifacts"
repository. Unit tests pass and the RC was built util JDK6.

The current code is available in branches/VFS-2.1 at r1741921. This is
what will be copied to tags upon successful passing of this vote.

This vote will be open for 72-hours, 2016/05/05 0500 UTC.

[ ] +1 Release these artifacts as version 2.1
[ ] 0 OK, but...
[ ] -1 I oppose these artifacts as version 2.1 because..

- Josh


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

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

[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 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  wrote:

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 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:
commons-vfs-2.1-bin
and
commons-vfs2-distribution-2.1-bin

etc.


Are they supposed to be the same? If not what is missing from one of them?

On 2 May 2016 at 10:40, sebb  wrote:

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 items as the above
URL is transitory.
The hashes allow one to tie the released files back to the vote thread.

They can be copied from the Nexus mail.


Artifacts:
https://dist.apache.org/repos/dist/dev/commons/vfs/{binaries,source}

Likewise here we include the revision id of the URL:

https://dist.apache.org/repos/dist/dev/commons/vfs/



Staged site:
http://home.apache.org/~elserj/commons/commons-vfs-2.1/index.html

There's no Clirr report that I could find.

Also the download page links to trunk rather than the specific tag.


All reports are available in the provided staged Maven site. JIRA-generated
release notes are available in the dist.a.o "Artifacts" repository. Unit
tests pass and the RC was built util JDK6.

E-mail should really have URL to make it easy for reviewers.


The current code is available in branches/VFS-2.1 at r1741921. This is what
will be copied to tags upon successful passing of this vote.

Full URLs in e-mails please.
Also it should be a TAG not a branch, as it should be kept if the vote
is successful


This vote will be open for 72-hours, 2016/05/05 0500 UTC.

   [ ] +1 Release these artifacts as version 2.1
   [ ] 0  OK, but...
   [X] -1 I oppose these artifacts as version 2.1 because..

As above.

No need necessarily to rebuild everything as most of the concerns
relate to the vote e-mail and the site.
e.g. you can rename the branch as a tag.


- 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-VFS2 2.1 rc0

[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 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 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  wrote:

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 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:
commons-vfs-2.1-bin
and
commons-vfs2-distribution-2.1-bin

etc.


Are they supposed to be the same? If not what is missing from one of them?

On 2 May 2016 at 10:40, sebb  wrote:

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 items as the above
URL is transitory.
The hashes allow one to tie the released files back to the vote thread.

They can be copied from the Nexus mail.


Artifacts:
https://dist.apache.org/repos/dist/dev/commons/vfs/{binaries,source}

Likewise here we include the revision id of the URL:

https://dist.apache.org/repos/dist/dev/commons/vfs/



Staged site:
http://home.apache.org/~elserj/commons/commons-vfs-2.1/index.html

There's no Clirr report that I could find.

Also the download page links to trunk rather than the specific tag.


All reports are available in the provided staged Maven site. JIRA-generated
release notes are available in the dist.a.o "Artifacts" repository. Unit
tests pass and the RC was built util JDK6.

E-mail should really have URL to make it easy for reviewers.


The current code is available in branches/VFS-2.1 at r1741921. This is what
will be copied to tags upon successful passing of this vote.

Full URLs in e-mails please.
Also it should be a TAG not a branch, as it should be kept if the vote
is successful


This vote will be open for 72-hours, 2016/05/05 0500 UTC.

   [ ] +1 Release these artifacts as version 2.1
   [ ] 0  OK, but...
   [X] -1 I oppose these artifacts as version 2.1 because..

As above.

No need necessarily to rebuild everything as most of the concerns
relate to the vote e-mail and the site.
e.g. you can rename the branch as a tag.


- 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-VFS2 2.1 rc0

[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 one to tie the released files back to the vote thread.


Ugh, this is what happens when I try to finish this up late at night :)

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

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

[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 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  wrote:
>> 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 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:
>> commons-vfs-2.1-bin
>> and
>> commons-vfs2-distribution-2.1-bin
>>
>> etc.
>>
>>
>> Are they supposed to be the same? If not what is missing from one of them?
>>
>> On 2 May 2016 at 10:40, sebb  wrote:
>>> 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 items as the above
>>> URL is transitory.
>>> The hashes allow one to tie the released files back to the vote thread.
>>>
>>> They can be copied from the Nexus mail.
>>>
 Artifacts:
 https://dist.apache.org/repos/dist/dev/commons/vfs/{binaries,source}
>>>
>>> Likewise here we include the revision id of the URL:
>>>
>>> https://dist.apache.org/repos/dist/dev/commons/vfs/
>>>
>>>
 Staged site:
 http://home.apache.org/~elserj/commons/commons-vfs-2.1/index.html
>>>
>>> There's no Clirr report that I could find.
>>>
>>> Also the download page links to trunk rather than the specific tag.
>>>
 All reports are available in the provided staged Maven site. JIRA-generated
 release notes are available in the dist.a.o "Artifacts" repository. Unit
 tests pass and the RC was built util JDK6.
>>>
>>> E-mail should really have URL to make it easy for reviewers.
>>>
 The current code is available in branches/VFS-2.1 at r1741921. This is what
 will be copied to tags upon successful passing of this vote.
>>>
>>> Full URLs in e-mails please.
>>> Also it should be a TAG not a branch, as it should be kept if the vote
>>> is successful
>>>
 This vote will be open for 72-hours, 2016/05/05 0500 UTC.

   [ ] +1 Release these artifacts as version 2.1
   [ ] 0  OK, but...
   [X] -1 I oppose these artifacts as version 2.1 because..
>>>
>>> As above.
>>>
>>> No need necessarily to rebuild everything as most of the concerns
>>> relate to the vote e-mail and the site.
>>> e.g. you can rename the branch as a tag.
>>>

 - 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: [CRYPTO] How to build CRYPTO on Mac OS 10.11?

[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 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: [CRYPTO] How to build CRYPTO on Mac OS 10.11?

[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 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...
>
> Yeah, you need a C compiler and linker set up and avail on the command
> line.
>

I have that set up. It looks like the build is missing required
libraries/dependencies, which were available on Mac OS prior to 10.11.

Benedikt


>
> Gary
> >
> > > 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
> >
>

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

[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
> > 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.


>
> > 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
>
>

Re: [LANG] Failing tests

[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 locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.11.4", arch: "x86_64", family: "mac"

I'll have more time to investigate this evening.

Benedikt

Chas Honton  schrieb am Mo., 2. Mai 2016 um 08:24 Uhr:

> 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 3.3.9 and Java
> 1.8.0_92.
>
> Chas
>
> > On May 1, 2016, at 12:20 PM, sebb  wrote:
> >
> >> On 1 May 2016 at 19:32, Benedikt Ritter  wrote:
> >> Hi,
> >>
> >> when building a clean checkout of Commons LANG, I get a lot of failing
> >> tests:
> >
> > OS?
> > Java?
> >
> >> Tests in error:
> >>  FastDateFormat_ParserTest>FastDateParserTest.testTzParses:265 »
> >> NullPointer
> >>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
> >> NullPointer
> >>  FastDateParserSDFTest.testUpperCase:134->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testUpperCase:134->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testUpperCase:134->checkParse:155 » NullPointer
> >>  FastDateParserSDFTest.testUpperCase:134->checkParse:155 » NullPointer
> >>  

Re: [VOTE] Apache Commons-VFS2 2.1 rc0

[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  wrote:
> 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 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:
> commons-vfs-2.1-bin
> and
> commons-vfs2-distribution-2.1-bin
>
> etc.
>
>
> Are they supposed to be the same? If not what is missing from one of them?
>
> On 2 May 2016 at 10:40, sebb  wrote:
>> 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 items as the above
>> URL is transitory.
>> The hashes allow one to tie the released files back to the vote thread.
>>
>> They can be copied from the Nexus mail.
>>
>>> Artifacts:
>>> https://dist.apache.org/repos/dist/dev/commons/vfs/{binaries,source}
>>
>> Likewise here we include the revision id of the URL:
>>
>> https://dist.apache.org/repos/dist/dev/commons/vfs/
>>
>>
>>> Staged site:
>>> http://home.apache.org/~elserj/commons/commons-vfs-2.1/index.html
>>
>> There's no Clirr report that I could find.
>>
>> Also the download page links to trunk rather than the specific tag.
>>
>>> All reports are available in the provided staged Maven site. JIRA-generated
>>> release notes are available in the dist.a.o "Artifacts" repository. Unit
>>> tests pass and the RC was built util JDK6.
>>
>> E-mail should really have URL to make it easy for reviewers.
>>
>>> The current code is available in branches/VFS-2.1 at r1741921. This is what
>>> will be copied to tags upon successful passing of this vote.
>>
>> Full URLs in e-mails please.
>> Also it should be a TAG not a branch, as it should be kept if the vote
>> is successful
>>
>>> This vote will be open for 72-hours, 2016/05/05 0500 UTC.
>>>
>>>   [ ] +1 Release these artifacts as version 2.1
>>>   [ ] 0  OK, but...
>>>   [X] -1 I oppose these artifacts as version 2.1 because..
>>
>> As above.
>>
>> No need necessarily to rebuild everything as most of the concerns
>> relate to the vote e-mail and the site.
>> e.g. you can rename the branch as a tag.
>>
>>>
>>> - 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-VFS2 2.1 rc0

[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 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:
commons-vfs-2.1-bin
and
commons-vfs2-distribution-2.1-bin

etc.


Are they supposed to be the same? If not what is missing from one of them?

On 2 May 2016 at 10:40, sebb  wrote:
> 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 items as the above
> URL is transitory.
> The hashes allow one to tie the released files back to the vote thread.
>
> They can be copied from the Nexus mail.
>
>> Artifacts:
>> https://dist.apache.org/repos/dist/dev/commons/vfs/{binaries,source}
>
> Likewise here we include the revision id of the URL:
>
> https://dist.apache.org/repos/dist/dev/commons/vfs/
>
>
>> Staged site:
>> http://home.apache.org/~elserj/commons/commons-vfs-2.1/index.html
>
> There's no Clirr report that I could find.
>
> Also the download page links to trunk rather than the specific tag.
>
>> All reports are available in the provided staged Maven site. JIRA-generated
>> release notes are available in the dist.a.o "Artifacts" repository. Unit
>> tests pass and the RC was built util JDK6.
>
> E-mail should really have URL to make it easy for reviewers.
>
>> The current code is available in branches/VFS-2.1 at r1741921. This is what
>> will be copied to tags upon successful passing of this vote.
>
> Full URLs in e-mails please.
> Also it should be a TAG not a branch, as it should be kept if the vote
> is successful
>
>> This vote will be open for 72-hours, 2016/05/05 0500 UTC.
>>
>>   [ ] +1 Release these artifacts as version 2.1
>>   [ ] 0  OK, but...
>>   [X] -1 I oppose these artifacts as version 2.1 because..
>
> As above.
>
> No need necessarily to rebuild everything as most of the concerns
> relate to the vote e-mail and the site.
> e.g. you can rename the branch as a tag.
>
>>
>> - 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-VFS2 2.1 rc0

[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 items as the above
URL is transitory.
The hashes allow one to tie the released files back to the vote thread.

They can be copied from the Nexus mail.

> Artifacts:
> https://dist.apache.org/repos/dist/dev/commons/vfs/{binaries,source}

Likewise here we include the revision id of the URL:

https://dist.apache.org/repos/dist/dev/commons/vfs/


> Staged site:
> http://home.apache.org/~elserj/commons/commons-vfs-2.1/index.html

There's no Clirr report that I could find.

Also the download page links to trunk rather than the specific tag.

> All reports are available in the provided staged Maven site. JIRA-generated
> release notes are available in the dist.a.o "Artifacts" repository. Unit
> tests pass and the RC was built util JDK6.

E-mail should really have URL to make it easy for reviewers.

> The current code is available in branches/VFS-2.1 at r1741921. This is what
> will be copied to tags upon successful passing of this vote.

Full URLs in e-mails please.
Also it should be a TAG not a branch, as it should be kept if the vote
is successful

> This vote will be open for 72-hours, 2016/05/05 0500 UTC.
>
>   [ ] +1 Release these artifacts as version 2.1
>   [ ] 0  OK, but...
>   [X] -1 I oppose these artifacts as version 2.1 because..

As above.

No need necessarily to rebuild everything as most of the concerns
relate to the vote e-mail and the site.
e.g. you can rename the branch as a tag.

>
> - 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

Build failed in Jenkins: Commons-CRYPTO #24

[Apache Jenkins Server]

See 

--
Started by user sdp
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu3 (Ubuntu ubuntu legacy-ubuntu) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/commons-crypto.git # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/commons-crypto.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/commons-crypto.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision c0c2e6fb98275a5b7445952ea5033c1c212e7601 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c0c2e6fb98275a5b7445952ea5033c1c212e7601
 > git rev-list c0c2e6fb98275a5b7445952ea5033c1c212e7601 # timeout=10
Setting MAVEN_3_0_4_HOME=/home/jenkins/tools/maven/apache-maven-3.0.4
Setting 
JDK_1_7_0_79_UNLIMITED_SECURITY__HOME=/home/jenkins/tools/java/jdk1.7.0_79-unlimited-security
Setting 
JDK1_8_0_66_UNLIMITED_SECURITY_HOME=/home/jenkins/tools/java/jdk1.8.0_66-unlimited-security
Parsing POMs
Modules changed, recalculating dependency graph
ERROR: Could not install MAVEN_3_0_4_HOME
java.lang.NullPointerException
at 
hudson.plugins.toolenv.ToolEnvBuildWrapper$1.buildEnvVars(ToolEnvBuildWrapper.java:46)
at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:947)
at 
hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:56)
at 
hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:166)
at hudson.plugins.git.GitSCM.getParamExpandedRepos(GitSCM.java:390)
at 
hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:577)
at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:527)
at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:381)
at hudson.scm.SCM.poll(SCM.java:398)
at hudson.model.AbstractProject._poll(AbstractProject.java:1453)
at hudson.model.AbstractProject.poll(AbstractProject.java:1356)
at 
jenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:526)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:555)
at 
hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
ERROR: Could not install JDK_1_7_0_79_UNLIMITED_SECURITY__HOME
java.lang.NullPointerException
at 
hudson.plugins.toolenv.ToolEnvBuildWrapper$1.buildEnvVars(ToolEnvBuildWrapper.java:46)
at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:947)
at 
hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:56)
at 
hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:166)
at hudson.plugins.git.GitSCM.getParamExpandedRepos(GitSCM.java:390)
at 
hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:577)
at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:527)
at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:381)
at hudson.scm.SCM.poll(SCM.java:398)
at hudson.model.AbstractProject._poll(AbstractProject.java:1453)
at hudson.model.AbstractProject.poll(AbstractProject.java:1356)
at 
jenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:526)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:555)
at 
hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
ERROR: Could not install JDK1_8_0_66_UNLIMITED_SECURITY_HOME
java.lang.NullPointerException
at 

Re: [LANG] Failing tests

[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 3.3.9 and Java 
1.8.0_92. 

Chas

> On May 1, 2016, at 12:20 PM, sebb  wrote:
> 
>> On 1 May 2016 at 19:32, Benedikt Ritter  wrote:
>> Hi,
>> 
>> when building a clean checkout of Commons LANG, I get a lot of failing
>> tests:
> 
> OS?
> Java?
> 
>> Tests in error:
>>  FastDateFormat_ParserTest>FastDateParserTest.testTzParses:265 »
>> NullPointer
>>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testLowerCasePP:149->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testLowerCase:144->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testOriginalPP:129->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testOriginal:124->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testUpperCasePP:139->checkParsePosition:195 »
>> NullPointer
>>  FastDateParserSDFTest.testUpperCase:134->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testUpperCase:134->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testUpperCase:134->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testUpperCase:134->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testUpperCase:134->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testUpperCase:134->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testUpperCase:134->checkParse:155 » NullPointer
>>  FastDateParserSDFTest.testUpperCase:134->checkParse:155 » NullPointer
>>  FastDateParserTest.testTzParses:265 » NullPointer
>>  FastDateParser_TimeZoneStrategyTest.testTimeZoneStrategyPattern:33 »
>> NullPointer
>> 
>> Tests run: 3802, Failures: 0, Errors: 51, Skipped: 5
>> 
>> Any idea about this?
>> 
>> Benedikt
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>