Re: [VOTE] Release Groovy 2.4.8

2017-01-09 Thread Guillaume Laforge
+1 (binding) I didn't check the signatures. But otherwise, the various notices files are there, I built from source successfully, I tried a few manual tests with the groovy, groovysh, and groovyConsole commands. All went totally fine. Guillaume On Mon, Jan 9, 2017 at 7:33 AM, Paul King wrote:

Re: [VOTE] Release Groovy 2.4.8

2017-01-09 Thread Cédric Champeau
+1 (binding) Signatures ok. SHA256 sum ok. Buildable from sources. Good work, Paul! 2017-01-09 7:33 GMT+01:00 Paul King : > Dear community, > > I am happy to start the VOTE thread for a Groovy 2.4.8 release! > > This release includes 84 bug fixes/improvements as outlined in the > changelog: >

Old Groovy Stuff on Maven2

2017-01-09 Thread jn0rthr
Have found this old groovy download package on maven2: http://repository.jboss.org/maven2/groovy/groovy-all/1.1-BETA-1/ and wonder if we have any responsibility to remove obsolete items like this ? -- View this message in context: http://groovy.329449.n5.nabble.com/Old-Groovy-Stuff-on-Maven2-

Re: Old Groovy Stuff on Maven2

2017-01-09 Thread Cédric Champeau
I see no good reason to remove any published artifact from a public repository. This would cause more troubles than benefits (I look at you, npm!). 2017-01-09 10:58 GMT+01:00 jn0rthr : > Have found this old groovy download package on maven2: > > http://repository.jboss.org/maven2/groovy/groovy-al

Re: Old Groovy Stuff on Maven2

2017-01-09 Thread Jim Northrop
Ok, so basically, we let sleeping dogs lie. ✅☺️ Sent from my iPad > On 9 Jan 2017, at 10:59, Cédric Champeau wrote: > > I see no good reason to remove any published artifact from a public > repository. This would cause more troubles than benefits (I look at you, > npm!). > > 2017-01-09 10:58

Re: Old Groovy Stuff on Maven2

2017-01-09 Thread Russel Winder
On Mon, 2017-01-09 at 12:14 +0100, Jim Northrop wrote: > Ok, so basically, we let sleeping dogs lie. ✅☺️ I think the policy has always been anything on Maven Central stays in Maven Central. Ignoring the quasi-"double entendre", if a release has been made it is never revoked – even releases that sh

Re: [VOTE] Release Groovy 2.4.8

2017-01-09 Thread Graeme Rocher
+1 (binding) Nice work Paul! On Mon, Jan 9, 2017 at 10:58 AM, Cédric Champeau wrote: > +1 (binding) > > Signatures ok. > SHA256 sum ok. > Buildable from sources. > > Good work, Paul! > > > 2017-01-09 7:33 GMT+01:00 Paul King : >> >> Dear community, >> >> I am happy to start the VOTE thread for a

Re: [VOTE] Release Groovy 2.4.8

2017-01-09 Thread Jim Jagielski
+1 (binding)! > On Jan 9, 2017, at 1:33 AM, Paul King wrote: > > Dear community, > > I am happy to start the VOTE thread for a Groovy 2.4.8 release! > > This release includes 84 bug fixes/improvements as outlined in the changelog: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?project

Re: [VOTE] Release Groovy 2.4.8

2017-01-09 Thread Jochen Theodorou
+1 On 09.01.2017 07:33, Paul King wrote: Dear community, I am happy to start the VOTE thread for a Groovy 2.4.8 release! This release includes 84 bug fixes/improvements as outlined in the changelog: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12335950 Tag

Re: MavenGrapeEngine?

2017-01-09 Thread Jochen Theodorou
well... contributions are welcome ;) On 06.01.2017 15:36, Romain Manni-Bucau wrote: 2017-01-06 15:33 GMT+01:00 Jochen Theodorou mailto:blackd...@gmx.org>>: On 06.01.2017 15:00, Romain Manni-Bucau wrote: [...] Means SNAPSHOT patterns needs to be identified (likely a flag in th

Re: rm servlet-api.jar?

2017-01-09 Thread Jochen Theodorou
On 06.01.2017 10:54, Romain Manni-Bucau wrote: Hi guys, Using groovy bundle (export PATH=$GROOVY_HOME/bin:$PATH) I often hit a blocker: servlet-api is there. It means that if you use tomcat you will use the wrong servlet api and get some troubles (missing message bundle, wrong version etc...).

Re: [VOTE] Release Groovy 2.4.8

2017-01-09 Thread John Wagenleitner
When I run `gradlew install` from source (both from the downloaded zip and from the GROOVY_2_4_8 tag) I get the error below. Looks like prior to commit 9fa4b015e4a80ef03 [1] this was a warning but now it fails the build and wont install the artifacts in the local maven repo. [1] https://github.co

Re: [VOTE] Release Groovy 2.4.8

2017-01-09 Thread Paul King
Can you check the version of gradle that is running? The artifacts are built using install and install works fine for me from the src zip. On Tue, Jan 10, 2017 at 12:33 PM, John Wagenleitner wrote: > When I run `gradlew install` from source (both from the downloaded zip and > from the GROOVY_2_4_

Re: [VOTE] Release Groovy 2.4.8

2017-01-09 Thread John Wagenleitner
With the downloaded source I was using gradle 2.14. I also fetched the GROOVY_2_4_8 tag and ran gradlew from there which is 2.3. I get the error with both. Not sure if I need to set up a property to point to gpg keys, but haven't had to do that in the past. On Mon, Jan 9, 2017 at 7:42 PM, Paul

Re: rm servlet-api.jar?

2017-01-09 Thread Romain Manni-Bucau
Le 10 janv. 2017 01:44, "Jochen Theodorou" a écrit : On 06.01.2017 10:54, Romain Manni-Bucau wrote: > Hi guys, > > Using groovy bundle (export PATH=$GROOVY_HOME/bin:$PATH) I often hit a > blocker: servlet-api is there. It means that if you use tomcat you will > use the wrong servlet api and get