Re: GGTS/ Eclipse support for the groovy ecosystem

Would it be fair to say there's not much appetite right now for framework support beyond groovy-the-language and gradle? Grails has quite a lot of usage, and they aren't going to upgrade to 3 all that quickly. Are the GGTS bits somehow encumbered beyond the groovy-eclipse plugin? Or just not of i

NSIS Groovy

Where is the source for the NSIS Groovy installers? The source for this used to be in SVN , but the only place I see it now is in Bintree .

RE: GGTS/ Eclipse support for the groovy ecosystem

> -Original Message- > From: Russel Winder [mailto:rus...@winder.org.uk] > Sent: Monday, April 06, 2015 11:01 AM > To: dev@groovy.incubator.apache.org > Subject: Re: GGTS/ Eclipse support for the groovy ecosystem > > On Mon, 2015-04-06 at 17:38 +0200, Cédric Champeau wrote: > […] > > As fo

Re: [Incubation] status

Le 06/04/15 18:31, Bertrand Delacretaz a écrit : > On Mon, Apr 6, 2015 at 6:19 PM, Cédric Champeau > wrote: >> I don't really understand the difference between "importing the code in an >> ASF repo" and "code initially imported" here. Could you elaborate what you >> mean?... > I'm not sure why Emm

Re: GGTS/ Eclipse support for the groovy ecosystem

On Mon, 2015-04-06 at 17:38 +0200, Cédric Champeau wrote: […] > As for maintaining Groovy Eclipse (not GGTS), we should really try > to find > a new team capable of handling this. It is basically a set of patches > applied on the Groovy compiler (that cannot be integrated into the > normal > comp

Re: [Incubation] status

On Mon, Apr 6, 2015 at 6:19 PM, Cédric Champeau wrote: > I don't really understand the difference between "importing the code in an > ASF repo" and "code initially imported" here. Could you elaborate what you > mean?... I'm not sure why Emmanuel mentions IP clearance, that's http://incubator.apac

Re: [Incubation] status

I don't really understand the difference between "importing the code in an ASF repo" and "code initially imported" here. Could you elaborate what you mean? Thanks! 2015-04-06 17:23 GMT+02:00 Bertrand Delacretaz : > Hi, > > On Mon, Apr 6, 2015 at 11:01 AM, Emmanuel Lécharny > wrote: > > ...Note

Re: GGTS/ Eclipse support for the groovy ecosystem

It's worth noting that Grails 3 doesn't need any particular IDE support apart from the Gradle one. So it should be compatible with the Community Edition AFAIK. As for maintaining Groovy Eclipse (not GGTS), we should really try to find a new team capable of handling this. It is basically a set of p

Re: [Incubation] status

Hi, On Mon, Apr 6, 2015 at 11:01 AM, Emmanuel Lécharny wrote: > ...Note that many of the cleanup tasks (ie, ASF headers, IP clearance and > such) can be done after this migratiuon !... IMO the IP clearance must happen before importing the code in an ASF repository - but for the code that's going

Re: GGTS/ Eclipse support for the groovy ecosystem

This is of course true. Unfortunately though, Grails support is not in the community edition, which is where the majority of requests to us on which IDE to pick come from ... I should probably have been clearer, as this is where GGTS tends to get it's users from, in my experience. It might be nic

Re: GGTS/ Eclipse support for the groovy ecosystem

Hi David, That would be nice if some Eclipse savvy people were able to pick up where Pivotal left. AFAIK Pivotal should continue a bit on the Groovy Eclipse plugin as it's required for Spring Boot, but to a minimal extent. But GGTS will be completely discontinued. Back on IntelliJ IDEA though, th

Re: What repository to use for pull request?

Yeah, I think for now, they're fine in our Groovy org on Github. We'll see later on if/when we want to introduce them as subproject at Apache or not. Guillaume 2015-04-06 14:27 GMT+02:00 Keegan Witt : > Will groovy-android-gradle-plugin, groovy-eclipse, and GMavenPlus remain > under the groovy o

GGTS/ Eclipse support for the groovy ecosystem

Hiya, I'm an intellij user‎. Many of the companies and individuals we work with, however, can't justify the cost of the ide, and so generally use GGTS as was. This has been moribund for quite a while, and is obviously now not going to be continued in its current form. I'm wondering, has there b

Incubator PMC/Board report for Apr 2015 ([ppmc])

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 15 April 2015, 10:30 am PST. The report for your podling will fo

Re: subscription request for dev

To subscribe send an e-mail to dev-subscr...@groovy.incubator.apache.org, you should receive an automated reply shortly asking you to confirm your subscription On Mon, Apr 6, 2015 at 9:20 AM jim northrop wrote: > pls include me in your mailing list - > > james.b.north...@googlemail.com >

Re: subscription request for dev

Hi Jim, The emails for subscribing are dev-subscr...@groovy.incubator.apache.org users-subscr...@groovy.incubator.apache.org I'm going to create a PR shortly to edit the mailing list page to add subscribe links. Several people have made this mistake alre

subscription request for dev

pls include me in your mailing list - james.b.north...@googlemail.com

Re: What repository to use for pull request?

Will groovy-android-gradle-plugin, groovy-eclipse, and GMavenPlus remain under the groovy org? -Keegan On Sun, Apr 5, 2015 at 12:18 PM, Guillaume Laforge wrote: > Hello Paolo, > > The sources haven't been moved just yet, so you can still do a pull request > at the usual place. > But later on, i

[ANN] JIRA moved to Apache

Hi all, Our *JIRA issue tracker moved* off from Codehaus and is now hosted at the Apache Software Foundation. Here's the new URL, please update your bookmarks: https://issues.apache.org/jira/browse/GROOVY/ Going forward, this is where you'll have to create new tickets. *Reminder:* Also, *don't

[Incubation] status

Hi guys, I have updated the Groovy status page : http://incubator.apache.org/projects/groovy.html There are a few remaining tasks to be completed, the main one being the migration of the source code to the Apache repository. This should be quite easy to do. Note that many of the cleanup tasks (i

Re: Unable to select 'Groovy' as the project when creating an issue on JIRA

Le 05/04/15 19:42, Shil Sinha a écrit : > Hi all, > > I am not seeing 'Groovy' listed in the projects dropdown when attempting to > create an issue on the Codehaus Jira. I have been able to create Groovy > issues in the past, and I am also able to select it as the project when > searching for issue

Pull request #651

Dear colleagues, I have failed build in current pull request. As I have found out my test fails only on Indy build for JDK7. Is it bug on my side or something wrong with using INVOKEDYNAMIC?? Best regards, Maksym Stavytskyi