Local trunk build failing for me - GroovyScriptEngineTest.testDynamicInstantiation()

[Roshan Dawrani-2]

Hi,
For me (on Widows XP), the local trunk build is failing due to GroovyScriptEngineTest.testDynamicInstantiation().

It fails with the following compilation error:

com.company.MakeMe: 10: unexpected token: package @ line 10, column 7.
               package com.company
         ^

I am also attaching the stack trace.

Anyone else seeing it?

-- Roshan

Testcase: testDynamicInstantiation took 0.08 sec
        Caused an ERROR
startup failed:
com.company.MakeMe: 10: unexpected token: package @ line 10, column 7.
       package com.company
         ^

1 error


        at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:296)
        at org.codehaus.groovy.control.ErrorCollector.addFatalError(ErrorCollector.java:143)
        at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:113)
        at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:125)
        at org.codehaus.groovy.control.SourceUnit.addError(SourceUnit.java:353)
        at org.codehaus.groovy.antlr.AntlrParserPlugin.transformCSTIntoAST(AntlrParserPlugin.java:102)
        at org.codehaus.groovy.antlr.AntlrParserPlugin.parseCST(AntlrParserPlugin.java:69)
        at org.codehaus.groovy.control.SourceUnit.parse(SourceUnit.java:249)
        at org.codehaus.groovy.control.CompilationUnit$1.call(CompilationUnit.java:155)
        at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:810)
        at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:470)
        at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:290)
        at groovy.util.GroovyScriptEngine$ScriptClassLoader.parseClass(GroovyScriptEngine.java:139)
        at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:261)
        at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:256)
        at groovy.lang.GroovyClassLoader.recompile(GroovyClassLoader.java:756)
        at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:716)
        at groovy.lang.GroovyClassLoader$InnerLoader.loadClass(GroovyClassLoader.java:424)
        at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:771)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:242)
        at java_lang_Class$forName$0.call(Unknown Source)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:133)
        at groovy.util.GroovyScriptEngineTest.instantiate(GroovyScriptEngineTest.groovy:156)
        at groovy.util.GroovyScriptEngineTest$instantiate.call(Unknown Source)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:129)
        at script.run(script.groovy:2)
        at groovy.util.GroovyScriptEngine.run(GroovyScriptEngine.java:401)
        at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229)
        at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:52)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:129)
        at groovy.util.GroovyScriptEngineTest.testDynamicInstantiation(GroovyScriptEngineTest.groovy:119)

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

    http://xircles.codehaus.org/manage_email

[Guillaume Laforge-2]

Hi Roshan,

Hmm... it's related to my recent commit about my partial fix of
GroovyScriptEngine's issues related to reloading / dependencies.
When working on that, I had that test failing too (although with a
different error), and when I committed my changes, my build was
running perfectly fine.
So I'm not sure what's failing here...

Guillaume

On Sun, Oct 11, 2009 at 11:03, Roshan Dawrani
<roshandawrani@...> wrote:

> Hi,
> For me (on Widows XP), the local trunk build is failing due to
> GroovyScriptEngineTest.testDynamicInstantiation().
>
> It fails with the following compilation error:
>
> com.company.MakeMe: 10: unexpected token: package @ line 10, column 7.
>                package com.company
>          ^
>
> I am also attaching the stack trace.
>
> Anyone else seeing it?
>
> -- Roshan
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

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

    http://xircles.codehaus.org/manage_email

[Roshan Dawrani-2]

I am a bit stuck with it. When I run just GroovyScriptEngineTest, it is going through fine, but with the full test run, one test in i is failing. And I wanted to avoid researching this one and focus on the one I am working on :-)

I had seen your recent mail about recent issues with GroovyScriptEngine, so thought that someone may have a quick remedy.

-- Roshan

On Sun, Oct 11, 2009 at 2:45 PM, Guillaume Laforge <glaforge@...> wrote:

Hi Roshan,

Hmm... it's related to my recent commit about my partial fix of
GroovyScriptEngine's issues related to reloading / dependencies.
When working on that, I had that test failing too (although with a
different error), and when I committed my changes, my build was
running perfectly fine.
So I'm not sure what's failing here...

Guillaume

On Sun, Oct 11, 2009 at 11:03, Roshan Dawrani
<roshandawrani@...> wrote:
> Hi,
> For me (on Widows XP), the local trunk build is failing due to
> GroovyScriptEngineTest.testDynamicInstantiation().
>
> It fails with the following compilation error:
>
> com.company.MakeMe: 10: unexpected token: package @ line 10, column 7.
>                package com.company
>          ^
>
> I am also attaching the stack trace.
>
> Anyone else seeing it?
>
> -- Roshan
>

> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>



--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

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

   http://xircles.codehaus.org/manage_email

[Guillaume Laforge-2]

Hi,

On Sun, Oct 11, 2009 at 11:21, Roshan Dawrani
<roshandawrani@...> wrote:
> I am a bit stuck with it. When I run just GroovyScriptEngineTest, it is
> going through fine, but with the full test run, one test in i is failing.
> And I wanted to avoid researching this one and focus on the one I am working
> on :-)

I understand, please temporarily disable it locally, till we find the problem.

> I had seen your recent mail about recent issues with GroovyScriptEngine, so
> thought that someone may have a quick remedy.

I ran another full build, and just running the single test case too,
and both ran fine here with Trunk.
Not sure yet what's causing this :-(

Guillaume

> -- Roshan
>
> On Sun, Oct 11, 2009 at 2:45 PM, Guillaume Laforge <glaforge@...>
> wrote:
>>
>> Hi Roshan,
>>
>> Hmm... it's related to my recent commit about my partial fix of
>> GroovyScriptEngine's issues related to reloading / dependencies.
>> When working on that, I had that test failing too (although with a
>> different error), and when I committed my changes, my build was
>> running perfectly fine.
>> So I'm not sure what's failing here...
>>
>> Guillaume
>>
>> On Sun, Oct 11, 2009 at 11:03, Roshan Dawrani
>> <roshandawrani@...> wrote:
>> > Hi,
>> > For me (on Widows XP), the local trunk build is failing due to
>> > GroovyScriptEngineTest.testDynamicInstantiation().
>> >
>> > It fails with the following compilation error:
>> >
>> > com.company.MakeMe: 10: unexpected token: package @ line 10, column 7.
>> >                package com.company
>> >          ^
>> >
>> > I am also attaching the stack trace.
>> >
>> > Anyone else seeing it?
>> >
>> > -- Roshan
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe from this list, please visit:
>> >
>> >    http://xircles.codehaus.org/manage_email
>> >
>> >
>>
>>
>>
>> --
>> Guillaume Laforge
>> Groovy Project Manager
>> Head of Groovy Development at SpringSource
>> http://www.springsource.com/g2one
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>

--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

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

    http://xircles.codehaus.org/manage_email

[Jochen Theodorou]

Roshan Dawrani schrieb:
> I am a bit stuck with it. When I run just GroovyScriptEngineTest, it is
> going through fine, but with the full test run, one test in i is
> failing. And I wanted to avoid researching this one and focus on the one
> I am working on :-)
>
> I had seen your recent mail about recent issues with GroovyScriptEngine,
> so thought that someone may have a quick remedy.

but.....
>      >
>      > It fails with the following compilation error:
>      >
>      > com.company.MakeMe: 10: unexpected token: package @ line 10, column 7.
>      >                package com.company
>      >          ^

that is an antlr error. That means the issue is related to a change in
the grammar. That means for me the changes to GSE are not at fault here.
It is much more possible that either my or your change to the grammar is
causing this.

bye blackdrag

--
Jochen "blackdrag" Theodorou
The Groovy Project Tech Lead (http://groovy.codehaus.org)
http://blackdragsview.blogspot.com/


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

    http://xircles.codehaus.org/manage_email

[Roshan Dawrani-2]

On Sun, Oct 11, 2009 at 2:59 PM, Jochen Theodorou <blackdrag@...> wrote:

Roshan Dawrani schrieb:

    > It fails with the following compilation error:
    >
    > com.company.MakeMe: 10: unexpected token: package @ line 10, column 7.
    >                package com.company
    >          ^

that is an antlr error. That means the issue is related to a change in the grammar. That means for me the changes to GSE are not at fault here. It is much more possible that either my or your change to the grammar is causing this.

The change I made to grammar y'day should not come into picture unless there is a try/catch block in script code, which is not the case with the case with the script being dynamically created here. After I am done with the little issue I am currently on, I will give a try and see what is causing the issue with this test.
 

bye blackdrag

--
Jochen "blackdrag" Theodorou
The Groovy Project Tech Lead (http://groovy.codehaus.org)
http://blackdragsview.blogspot.com/

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

  http://xircles.codehaus.org/manage_email

[Roshan Dawrani-2]

Looked into the error and it is not due to any grammar misbehavior. It is a temp file clean-up issue.

The dynamically created file dynamicSrcRootToBeDeleted\com\company\MakeMe.groovy has the contents like below (class definition code repeated 'n' times - hence the compilation failure):

==============================

            package com.company

            class MakeMe extends MakeMeSuper{
               def modifyWidth(dim, addThis){
                  dim.width += addThis
               }
            }   
         
            package com.company

            class MakeMe extends MakeMeSuper{
               def modifyWidth(dim, addThis){
                  dim.width += addThis
               }
            }   
......
**** above class def repeated n times because clean-up did not happen and stuff kept getting appended ****
......
==============================

The same issue is not there with other scripts. They seem to have the right contents.

The GroovyScriptEngineTest code also seems fine - in that it is trying to delete the files correctly - problem is that it is not happening as expected.

In any case, now I am able to manually delete the foler "dynamicSrcRootToBeDeleted" to run the test suite and proceed :-)

To get rid of this "delete" issue, can the existing content (won't be any if file got deleted as expected) be overwritten first and then code appended?

-- Roshan

On Sun, Oct 11, 2009 at 3:06 PM, Roshan Dawrani <roshandawrani@...> wrote:

On Sun, Oct 11, 2009 at 2:59 PM, Jochen Theodorou <blackdrag@...> wrote:

Roshan Dawrani schrieb:

    > It fails with the following compilation error:
    >
    > com.company.MakeMe: 10: unexpected token: package @ line 10, column 7.
    >                package com.company
    >          ^

that is an antlr error. That means the issue is related to a change in the grammar. That means for me the changes to GSE are not at fault here. It is much more possible that either my or your change to the grammar is causing this.

The change I made to grammar y'day should not come into picture unless there is a try/catch block in script code, which is not the case with the case with the script being dynamically created here. After I am done with the little issue I am currently on, I will give a try and see what is causing the issue with this test.
 

bye blackdrag

--
Jochen "blackdrag" Theodorou
The Groovy Project Tech Lead (http://groovy.codehaus.org)
http://blackdragsview.blogspot.com/

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

  http://xircles.codehaus.org/manage_email

[Guillaume Laforge-2]

Hi Roshan,

Could you please try with the attached patch to see if it's working
fine on your setup?
It works for me, both when running the test alone, or during the full test run.

Guillaume


On Sun, Oct 11, 2009 at 13:35, Roshan Dawrani
<roshandawrani@...> wrote:

> Looked into the error and it is not due to any grammar misbehavior. It is a
> temp file clean-up issue.
>
> The dynamically created file
> dynamicSrcRootToBeDeleted\com\company\MakeMe.groovy has the contents like
> below (class definition code repeated 'n' times - hence the compilation
> failure):
>
> ==============================
>
>             package com.company
>
>             class MakeMe extends MakeMeSuper{
>                def modifyWidth(dim, addThis){
>                   dim.width += addThis
>                }
>             }
>
>             package com.company
>
>             class MakeMe extends MakeMeSuper{
>                def modifyWidth(dim, addThis){
>                   dim.width += addThis
>                }
>             }
> ......
> **** above class def repeated n times because clean-up did not happen and
> stuff kept getting appended ****
> ......
> ==============================
>
> The same issue is not there with other scripts. They seem to have the right
> contents.
>
> The GroovyScriptEngineTest code also seems fine - in that it is trying to
> delete the files correctly - problem is that it is not happening as
> expected.
>
> In any case, now I am able to manually delete the foler
> "dynamicSrcRootToBeDeleted" to run the test suite and proceed :-)
>
> To get rid of this "delete" issue, can the existing content (won't be any if
> file got deleted as expected) be overwritten first and then code appended?
>
> -- Roshan
>
>
> On Sun, Oct 11, 2009 at 3:06 PM, Roshan Dawrani <roshandawrani@...>
> wrote:
>>
>> On Sun, Oct 11, 2009 at 2:59 PM, Jochen Theodorou <blackdrag@...>
>> wrote:
>>>
>>> Roshan Dawrani schrieb:
>>>>
>>>>     > It fails with the following compilation error:
>>>>     >
>>>>     > com.company.MakeMe: 10: unexpected token: package @ line 10,
>>>> column 7.
>>>>     >                package com.company
>>>>     >          ^
>>>
>>> that is an antlr error. That means the issue is related to a change in
>>> the grammar. That means for me the changes to GSE are not at fault here. It
>>> is much more possible that either my or your change to the grammar is
>>> causing this.
>>
>> The change I made to grammar y'day should not come into picture unless
>> there is a try/catch block in script code, which is not the case with the
>> case with the script being dynamically created here. After I am done with
>> the little issue I am currently on, I will give a try and see what is
>> causing the issue with this test.
>>
>>>
>>> bye blackdrag
>>>
>>> --
>>> Jochen "blackdrag" Theodorou
>>> The Groovy Project Tech Lead (http://groovy.codehaus.org)
>>> http://blackdragsview.blogspot.com/
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>   http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>
>

--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one


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

    http://xircles.codehaus.org/manage_email

[Roshan Dawrani-2]

Hi Guillaume,
I applied the patch and did the full build a few times and ran into no issues.

Thanks.
Roshan

On Mon, Oct 12, 2009 at 12:03 AM, Guillaume Laforge <glaforge@...> wrote:

Hi Roshan,

Could you please try with the attached patch to see if it's working
fine on your setup?
It works for me, both when running the test alone, or during the full test run.

Guillaume


On Sun, Oct 11, 2009 at 13:35, Roshan Dawrani

<roshandawrani@...> wrote:
> Looked into the error and it is not due to any grammar misbehavior. It is a
> temp file clean-up issue.
>
> The dynamically created file
> dynamicSrcRootToBeDeleted\com\company\MakeMe.groovy has the contents like
> below (class definition code repeated 'n' times - hence the compilation
> failure):
>
> ==============================
>
>             package com.company
>
>             class MakeMe extends MakeMeSuper{
>                def modifyWidth(dim, addThis){
>                   dim.width += addThis
>                }
>             }
>
>             package com.company
>
>             class MakeMe extends MakeMeSuper{
>                def modifyWidth(dim, addThis){
>                   dim.width += addThis
>                }
>             }
> ......
> **** above class def repeated n times because clean-up did not happen and
> stuff kept getting appended ****
> ......
> ==============================
>
> The same issue is not there with other scripts. They seem to have the right
> contents.
>
> The GroovyScriptEngineTest code also seems fine - in that it is trying to
> delete the files correctly - problem is that it is not happening as
> expected.
>
> In any case, now I am able to manually delete the foler
> "dynamicSrcRootToBeDeleted" to run the test suite and proceed :-)
>
> To get rid of this "delete" issue, can the existing content (won't be any if
> file got deleted as expected) be overwritten first and then code appended?
>
> -- Roshan
>
>
> On Sun, Oct 11, 2009 at 3:06 PM, Roshan Dawrani <roshandawrani@...>
> wrote:
>>
>> On Sun, Oct 11, 2009 at 2:59 PM, Jochen Theodorou <blackdrag@...>
>> wrote:
>>>
>>> Roshan Dawrani schrieb:
>>>>
>>>>     > It fails with the following compilation error:
>>>>     >
>>>>     > com.company.MakeMe: 10: unexpected token: package @ line 10,
>>>> column 7.
>>>>     >                package com.company
>>>>     >          ^
>>>
>>> that is an antlr error. That means the issue is related to a change in
>>> the grammar. That means for me the changes to GSE are not at fault here. It
>>> is much more possible that either my or your change to the grammar is
>>> causing this.
>>
>> The change I made to grammar y'day should not come into picture unless
>> there is a try/catch block in script code, which is not the case with the
>> case with the script being dynamically created here. After I am done with
>> the little issue I am currently on, I will give a try and see what is
>> causing the issue with this test.
>>
>>>
>>> bye blackdrag
>>>
>>> --
>>> Jochen "blackdrag" Theodorou
>>> The Groovy Project Tech Lead (http://groovy.codehaus.org)
>>> http://blackdragsview.blogspot.com/
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>>   http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>
>

--

Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

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

   http://xircles.codehaus.org/manage_email

[Guillaume Laforge-2]

Hi Roshan,

I'm committing those changes.
To the 1.6 branch as well.
Thanks for trying out the patch.

Guillaume

On Mon, Oct 12, 2009 at 07:54, Roshan Dawrani
<roshandawrani@...> wrote:

> Hi Guillaume,
> I applied the patch and did the full build a few times and ran into no
> issues.
>
> Thanks.
> Roshan
>
> On Mon, Oct 12, 2009 at 12:03 AM, Guillaume Laforge <glaforge@...>
> wrote:
>>
>> Hi Roshan,
>>
>> Could you please try with the attached patch to see if it's working
>> fine on your setup?
>> It works for me, both when running the test alone, or during the full test
>> run.
>>
>> Guillaume
>>
>>
>> On Sun, Oct 11, 2009 at 13:35, Roshan Dawrani
>> <roshandawrani@...> wrote:
>> > Looked into the error and it is not due to any grammar misbehavior. It
>> > is a
>> > temp file clean-up issue.
>> >
>> > The dynamically created file
>> > dynamicSrcRootToBeDeleted\com\company\MakeMe.groovy has the contents
>> > like
>> > below (class definition code repeated 'n' times - hence the compilation
>> > failure):
>> >
>> > ==============================
>> >
>> >             package com.company
>> >
>> >             class MakeMe extends MakeMeSuper{
>> >                def modifyWidth(dim, addThis){
>> >                   dim.width += addThis
>> >                }
>> >             }
>> >
>> >             package com.company
>> >
>> >             class MakeMe extends MakeMeSuper{
>> >                def modifyWidth(dim, addThis){
>> >                   dim.width += addThis
>> >                }
>> >             }
>> > ......
>> > **** above class def repeated n times because clean-up did not happen
>> > and
>> > stuff kept getting appended ****
>> > ......
>> > ==============================
>> >
>> > The same issue is not there with other scripts. They seem to have the
>> > right
>> > contents.
>> >
>> > The GroovyScriptEngineTest code also seems fine - in that it is trying
>> > to
>> > delete the files correctly - problem is that it is not happening as
>> > expected.
>> >
>> > In any case, now I am able to manually delete the foler
>> > "dynamicSrcRootToBeDeleted" to run the test suite and proceed :-)
>> >
>> > To get rid of this "delete" issue, can the existing content (won't be
>> > any if
>> > file got deleted as expected) be overwritten first and then code
>> > appended?
>> >
>> > -- Roshan
>> >
>> >
>> > On Sun, Oct 11, 2009 at 3:06 PM, Roshan Dawrani
>> > <roshandawrani@...>
>> > wrote:
>> >>
>> >> On Sun, Oct 11, 2009 at 2:59 PM, Jochen Theodorou <blackdrag@...>
>> >> wrote:
>> >>>
>> >>> Roshan Dawrani schrieb:
>> >>>>
>> >>>>     > It fails with the following compilation error:
>> >>>>     >
>> >>>>     > com.company.MakeMe: 10: unexpected token: package @ line 10,
>> >>>> column 7.
>> >>>>     >                package com.company
>> >>>>     >          ^
>> >>>
>> >>> that is an antlr error. That means the issue is related to a change in
>> >>> the grammar. That means for me the changes to GSE are not at fault
>> >>> here. It
>> >>> is much more possible that either my or your change to the grammar is
>> >>> causing this.
>> >>
>> >> The change I made to grammar y'day should not come into picture unless
>> >> there is a try/catch block in script code, which is not the case with
>> >> the
>> >> case with the script being dynamically created here. After I am done
>> >> with
>> >> the little issue I am currently on, I will give a try and see what is
>> >> causing the issue with this test.
>> >>
>> >>>
>> >>> bye blackdrag
>> >>>
>> >>> --
>> >>> Jochen "blackdrag" Theodorou
>> >>> The Groovy Project Tech Lead (http://groovy.codehaus.org)
>> >>> http://blackdragsview.blogspot.com/
>> >>>
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe from this list, please visit:
>> >>>
>> >>>   http://xircles.codehaus.org/manage_email
>> >>>
>> >>>
>> >>
>> >
>> >
>>
>>
>>
>> --
>> Guillaume Laforge
>> Groovy Project Manager
>> Head of Groovy Development at SpringSource
>> http://www.springsource.com/g2one
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>
>

--
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

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

    http://xircles.codehaus.org/manage_email