Re: [VOTE][JCS] release [jcs] 2.0-beta-1 (take 4)

+1 On 20 February 2015 at 00:28, Romain Manni-Bucau wrote: > Hi > > Another try, hopefully right this time (I speak about JCS in a JUG > next thursday so would be awesome to have a release ;)) > > - here is the maven repo: > https://repository.apache.org/content/repositories/orgapachecommons-108

[RESULT][VOTE][JCS] release [jcs] 2.0-beta-1 (take 4)

So with 3 +1s bindings and 2 +1s non-bindings and no other vote this vote passes. I'll publish the artifacts and ask some help for the website since I never did it yet. Thank you all for the votes and your patience! Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wor

Re: [VOTE][JCS] release [jcs] 2.0-beta-1 (take 4)

On 19.02.15 14:28, Romain Manni-Bucau wrote: > Hi > > Another try, hopefully right this time (I speak about JCS in a JUG > next thursday so would be awesome to have a release ;)) > > - here is the maven repo: > https://repository.apache.org/content/repositories/orgapachecommons-1083/ > - assembli

Re: [VOTE][JCS] release [jcs] 2.0-beta-1 (take 4)

Build succeeds on OSX java version "1.7.0_71" Java(TM) SE Runtime Environment (build 1.7.0_71-b14) Failed on 1.8 due to javadoc whining Contents look OK, sigs and hashes are good. Two nits: * Release notes should be included with source and binary release tarballs * BUILDING.txt has a typo - s/i

Re: [VOTE][JCS] release [jcs] 2.0-beta-1 (take 4)

Build was successful (in half an hour) on Windows 8.1 with JDK 1.6. Artifacts and site look good. Nits: - The sources artifacts in the binary distribution contain spurious directories. - IMHO a 2.0 release should have a file with release notes included describing the possibly breaking changes to t

Re: [VOTE][JCS] release [jcs] 2.0-beta-1 (take 4)

done Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2015-02-19 22:27 GMT+01:00 Romain Manni-Bucau : > Oops you are right, forgot I changed of key with my hard drive :s. My > key can be found in http://svn.apache.org/repos

Re: [VOTE][JCS] release [jcs] 2.0-beta-1 (take 4)

Oops you are right, forgot I changed of key with my hard drive :s. My key can be found in http://svn.apache.org/repos/asf/geronimo/KEYS. I'll add it in commons tomorrow. Sorry again Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmann

Re: [VOTE][JCS] release [jcs] 2.0-beta-1 (take 4)

Hi, maybe the problem is on my side (it has been a long day), but I am not able to verify the signature of the distributions: $ gpg --verify commons-jcs-dist-2.0-beta-1-src.zip.asc gpg: Signature made 02/19/15 11:51:21 using RSA key ID DDB37997 gpg: Can't check signature: public key not found I

Re: [VOTE][JCS] release [jcs] 2.0-beta-1 (take 4)

Thank you, Romain! Builds fine; no errors, no warnings - have not checked for other issues; so here's my non-binding +1; I'm hardly waiting for a (beta) release, as I'd like to replace old JSC in an application of mine... Johannes mvn -version Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8

[VOTE][JCS] release [jcs] 2.0-beta-1 (take 4)

Hi Another try, hopefully right this time (I speak about JCS in a JUG next thursday so would be awesome to have a release ;)) - here is the maven repo: https://repository.apache.org/content/repositories/orgapachecommons-1083/ - assemblies can be found here https://repository.apache.org/content/re