gmane.comp.lang.groovy.devel

Re: [groovy-dev] Literate Groovy or Allowing transformation at INITIALIZATION phase

Chanwit Kaewkasi — 2013-05-24T05:51:16

Thanks, Guillaume. That's neat !

Best regards,

-chanwit

--
Chanwit Kaewkasi
linkedin.com/in/chanwit


On Fri, May 24, 2013 at 2:11 AM, Guillaume Laforge
<glaforge-yCVjj/EcxBJg9hUCZPvPmw< at >public.gmane.org> wrote:

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Re: [groovy-dev] Literate Groovy or Allowing transformation at INITIALIZATION phase

Guillaume Laforge — 2013-05-23T19:11:54

Hi Chanwit,

I had some fun along those lines a while ago with Markdown and Groovy.

I put an example on the Groovy console here:
http://groovyconsole.appspot.com/script/986001

It's one approach of doing so.

With your approach, instead of actually looking at the INITIALIZATION
phase, you'd better look at creating and plugin your own AntlrParserPlugin,
which is where you could preprocess the source text which is fed to the
compiler -- notice setPluginFactory() method on CompilerConfiguration.

And also with the recent --configscript option, you might also be able to
configure that parser plugin for files with a certain extension...

It's pretty straightforward to do literate programming with Groovy and some
markup library, and it's quite fun :-)

Guillaume


On Thu, May 23, 2013 at 5:37 PM, Chanwit Kaewkasi <chanwit-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: [groovy-dev] Make NodeChildren and Attributes public in GROOVY_2_1_X?

Tim Yates — 2013-05-23T18:46:54

Cool! :-)
On 22 May 2013 22:11, "Paul King" <paulk-V+QuBFElvc30CCvOHzKKcA< at >public.gmane.org> wrote:

[groovy-dev] Literate Groovy or Allowing transformation at INITIALIZATION phase

Chanwit Kaewkasi — 2013-05-23T15:37:21

The idea is taken from Literate CoffeeScript:

https://github.com/github/markup/pull/192

and I know that there's the INITIALIZATION phase in the Groovy
compiler. But at the moment, it does not allow to perform any action
there without tweaking the compiler itself.

My idea is that it would be wonderful to take a Markdown (.md) source
file in, and we can have a trasformer at the INITIALIZATION phase.
Then we can do some pre-processing there. In this case, changing .md
source file into Groovy syntax.

There are several advantages. Here's a list I am thinking of:

1. This will allow us to embed Groovy into other mini-languages. In
this example, I'm trying to embed Groovy into Markdown.
2. Other mini-languages can be sharing the same class loader with
Groovy. It's a form of joint compilation.
3. IDE support for these mini-languages is enabled by default because
of Groovy. Imagin that I can right-click on .md file and Run it. Then
it becomes a JUnit test case.

The very first think I am concerning here is that w

Re: [groovy-dev] sorry for breaking the build / groovy-groovysh tests

Pascal Schumacher — 2013-05-22T21:18:35

Forgot to mention: I updated the pull request 
(https://github.com/groovy/groovy-core/pull/194) to notify tkurse of the 
failures.

Am 22.05.2013 23:16, schrieb Pascal Schumacher:


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[groovy-dev] sorry for breaking the build / groovy-groovysh tests

Pascal Schumacher — 2013-05-22T21:16:13

Hello everybody,

sorry for breaking the build again. I reviewed the code of the pull 
requests, merged them into my local repo and run "gradle clean test". 
Everything looked fine.

I can now reproduce the failures but only by running "gradle test" from 
/subprojects/groovy-groovysh. Anybody has an idea why I need to call 
that? I guess the new test for groovysh are missing from some uebertestcase?

Sadly I do not know enought about groovy mocking/stubbing to fix the 
tests this evening and get the build green again.

Sorry again,
Pascal



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Re: [groovy-dev] Make NodeChildren and Attributes public in GROOVY_2_1_X?

Paul King — 2013-05-22T21:11:23

We should merge that change ... and done.

Cheers, Paul.

On 23/05/2013 12:47 AM, Tim Yates wrote:


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Re: [groovy-dev] Gradle upgrade

Pascal Schumacher — 2013-05-22T16:45:59

You are correct, the failures of this test are not related to the gradle 
version.

In an effort to speed-up the groovy test execution time 
(http://jira.codehaus.org/browse/GROOVY-6081) I reduced the sleep() time 
of this test to 1/10. This was probably too much, as this test also 
fails on the build server from time to time. I therefore increased the 
sleep() time a bit 
(https://github.com/groovy/groovy-core/commit/1c7f8f36ac543f81a695a997a6f531e7177acdd3).

Sorry about that,
Pascal

Am 22.05.2013 11:59, schrieb Andrey Bloschetsov:

[groovy-dev] Make NodeChildren and Attributes public in GROOVY_2_1_X?

Tim Yates — 2013-05-22T14:47:00

Hi all, there's this commit to master back in March

https://github.com/groovy/groovy-core/commit/0e16db0bf6acb9ba98b418c372536f713f8a8ea9

Which hasn't made it into the 2.1.X branch.  It seems someone is having
problems with it

http://stackoverflow.com/questions/16694074/referring-to-nodechildren-in-groovy-code

Is there any outstanding reason we can't cherry-pick this commit into the
branch from master?

Cheers,

Tim

Re: [groovy-dev] Gradle upgrade

Andrey Bloschetsov — 2013-05-22T09:59:22

Hmmm.. Sometimes I have groovy.GroovyMethodsTest.testObjectSleep FAILED.
It's happens periodically on '$ gradle clean build' and perhaps, it's
not depends of Gradle version.

Just in case I attach a report.

2013/5/22 Guillaume Laforge <glaforge-yCVjj/EcxBJg9hUCZPvPmw< at >public.gmane.org>:

Re: [groovy-dev] Gradle upgrade

Guillaume Laforge — 2013-05-22T09:14:38

A test build worked too.


On Wed, May 22, 2013 at 11:03 AM, Guillaume Laforge
<glaforge-yCVjj/EcxBJg9hUCZPvPmw< at >public.gmane.org>wrote:

Re: [groovy-dev] Gradle upgrade

Guillaume Laforge — 2013-05-22T09:03:53

I just ran a quick gradle clean installGroovy with Gradle 1.6 and it worked
fine for me on my Mac.
Haven't tried our other usual tasks yet.


On Wed, May 22, 2013 at 10:53 AM, Andrey Bloschetsov
<bloschetsov-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>wrote:

Re: [groovy-dev] Gradle upgrade

Andrey Bloschetsov — 2013-05-22T08:53:36

Hi Russel,

With version 1.6 build will fail, but if use '--no-daemon', then build
will be successful.

$ gradle --version
------------------------------------------------------------
Gradle 1.6
------------------------------------------------------------

Gradle build time: Tuesday, May 7, 2013 9:12:14 AM UTC
Groovy: 1.8.6
Ant: Apache Ant(TM) version 1.8.4 compiled on May 22 2012
Ivy: 2.2.0
JVM: 1.7.0_21 (Oracle Corporation 23.21-b01)
OS: Linux 3.8.0-21-generic amd64

2013/5/22 Russel Winder <russel-URxFuvIByzTe9xe1eoZjHA< at >public.gmane.org>:

[groovy-dev] Gradle upgrade

Russel Winder — 2013-05-22T06:22:49

Groovy build uses Gradle 1.5 anyone tried 1.6?

Aw: Re: [groovy-dev] GROOVY-5492

Pascal Schumacher — 2013-05-17T14:46:42

Re: [groovy-dev] GROOVY-5492

Andrey Bloschetsov — 2013-05-17T12:10:40

Hello Guillaume,

Thanks for your motivation :)

2013/5/17 Guillaume Laforge <glaforge-yCVjj/EcxBJg9hUCZPvPmw< at >public.gmane.org>:

Re: [groovy-dev] GROOVY-5492

Andrey Bloschetsov — 2013-05-17T12:10:19

Hello Pascal,

2013/5/17 Pascal Schumacher <PascalSchumacher-hi6Y0CQ0nG0< at >public.gmane.org>:

OK, I'll deal with it.


Thank you for information, I didn't know about it. I think it would be
helpful to place this information on
http://groovy.codehaus.org/Contributing. Not sure exactly, but it
seems I can add this information myself, of course if nobody do not
mind.




--
Andrey Bloschetsov

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Re: [groovy-dev] GROOVY-5492

Guillaume Laforge — 2013-05-17T08:10:12

Hello Andrey,

It's not assigned, and I don't think anybody's looking at the issue right
now.
So feel free to start working on it!
And don't hesitate to come back to us if you have any question.

Looking forward to your contribution!

Guillaume



On Fri, May 17, 2013 at 9:52 AM, Andrey Bloschetsov
<bloschetsov-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>wrote:

Aw: [groovy-dev] GROOVY-5492

Pascal Schumacher — 2013-05-17T08:08:24

[groovy-dev] GROOVY-5492

Andrey Bloschetsov — 2013-05-17T07:52:05

Hello everybody,

I found the GROOVY-5492 (https://jira.codehaus.org/browse/GROOVY-5492)
in the issues for contributors. I think, I could be fix this issue.
Someone is now engaged with this issue?

--
Andrey Bloschetsov

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Re: [groovy-dev] Jira Registration

Pascal Schumacher — 2013-05-12T10:04:21

Thanks. :)

I added these instructions to the 
http://docs.codehaus.org/display/GROOVY/Contributing page.

Kind regards,
Pascal

Am 10.05.2013 19:46, schrieb Alan Thompson:


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email