[ANN] Groovy Weekly #70

Hi all, It's already Wednesday here, but still Tuesday in Americas, so here's Groovy Weekly #70! http://glaforge.appspot.com/article/groovy-weekly-70 Keep on groovy-ing, and remember to subscribe to the new mailing-lists ! -- Guillaume Laforge Groo

Re: In shape for a 2.4.4 release?

Le 19/05/15 21:36, Cédric Champeau a écrit : > Hi guys, > > I wanted to check with you what is preventing us from releasing 2.4.4. > Apart from the usual bugfixes, I think the necessary work on the source > code itself to match the Apache guidance has been done (in particular > licenses checks). >

Re: In shape for a 2.4.4 release?

2015-05-19 21:59 GMT+02:00 Andrew Bayer : > Source artifacts will need to be posted to dist.apache.org - that's the > canonical location for all Apache releases. > Yup, if it wasn't clear, that was what I meant with "release manager has to copy to [1]". > We'll also need to make sure that http://

Re: In shape for a 2.4.4 release?

2015-05-19 21:59 GMT+02:00 Keegan Witt : > If they require -incubating in the filename, does that mean it'll be in > the Maven coordinates as well? If so, that's unfortunate since there are > many tools (like IntelliJ) that probably won't be able to automatically > locate the source jar. > > No,

Re: In shape for a 2.4.4 release?

The Maven sources.jar will have the same version as the other Maven artifacts - the sources zip referred to here is the source release tarball/zipfile that is the only actual official Apache release artifact - https://dist.apache.org/repos/dist/release/jclouds/1.9.0/, e.g. A. On Tue, May 19, 2015

Re: In shape for a 2.4.4 release?

If they require -incubating in the filename, does that mean it'll be in the Maven coordinates as well? If so, that's unfortunate since there are many tools (like IntelliJ) that probably won't be able to automatically locate the source jar. -Keegan On Tue, May 19, 2015 at 3:36 PM, Cédric Champeau

Re: In shape for a 2.4.4 release?

Source artifacts will need to be posted to dist.apache.org - that's the canonical location for all Apache releases. We'll also need to make sure that http://creadur.apache.org/rat/ verifies that we don't have license issues, etc - looks like Samza has done some of the work for integrating Gradle an

In shape for a 2.4.4 release?

Hi guys, I wanted to check with you what is preventing us from releasing 2.4.4. Apart from the usual bugfixes, I think the necessary work on the source code itself to match the Apache guidance has been done (in particular licenses checks). >From my perspective it should be possible to release us

Re: TestNG Update

But we'd love to welcome you as a committer to increase our community (it's an Apache thing too) :-) Guillaume 2015-05-19 20:37 GMT+02:00 Russel Winder : > On Tue, 2015-05-19 at 15:58 +0200, Guillaume Laforge wrote: > > What about a pull request? ;-) > > Because Paul King has already done it? >

Re: TestNG Update

On Tue, 2015-05-19 at 15:58 +0200, Guillaume Laforge wrote: > What about a pull request? ;-) Because Paul King has already done it? PS I am trying to preserve my status as a member of the Groovy community who has no commits in the code base. It's an Apache thing. -- Russel. ===

Re: TestNG Update

It's okay, I have the test suite running with that version now to check if all still in order. Paul. On 19/05/2015 11:58 PM, Guillaume Laforge wrote: What about a pull request? ;-) 2015-05-19 14:31 GMT+02:00 Russel Winder mailto:rus...@winder.org.uk>>: Can someone add an update of TestN

Re: TestNG Update

What about a pull request? ;-) 2015-05-19 14:31 GMT+02:00 Russel Winder : > Can someone add an update of TestNG from 6.8.13 to 6.9.4 as an > addendum to a near term commit? > -- > Russel. > > = > Dr Russel Winder t:

TestNG Update

Can someone add an update of TestNG from 6.8.13 to 6.9.4 as an addendum to a near term commit? -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 46