Re: [groovy-user] java.lang.ClassFormatError exception with 1.1 rc1

Hi, Guillaume & Jochen

Thank you very much.
It works well when I use the groovy-1.1-rc2-SNAPSHOT.Jar.

greetings,
dongdong

Guillaume Laforge wrote:
> On 10/31/07, Jochen Theodorou <blackdrag@...> wrote:
>   
>> [...]
>> If you want to make
>> sure, then I suggest, that you try our head revision fro svn... there
>> would still be a little bit of time to fix that if the error is still there
>>     
>
> If you want to test the version in SVN, you can download a jar from
> our CI server:
> http://build.canoo.com/groovy/
>
>   

--

-- 

Würth Phoenix Information Technology (Shanghai) Co., Ltd.
Dongdong Xu
Product Development

Building 9, Capital of Leaders, No.1387, ZhangDong Rd.

Re: [groovy-user] tooltiptext...

Re: [groovy-user] Java vs Groovy Differences

We discussed them at Groovy DevCon #4, and we may support them.
Once we release 1.1 in about 10 days, we'll work on the exact roadmap
for the future.

On 10/31/07, Krieg, Adam <Adam.Krieg@...> wrote:
> Are nested classes on the todo list?
>
> -----Original Message-----
> From: Guillaume Laforge [mailto:glaforge@...]
> Sent: Wednesday, October 31, 2007 5:30 PM
> To: user@...
> Subject: Re: [groovy-user] Java vs Groovy Differences
>
> On 10/31/07, Geertjan <Geertjan.Wielenga@...> wrote:
> > James Williams wrote:
> > > There is http://groovy.codehaus.org/Differences+from+Java.
> > > <http://groovy.codehaus.org/Differences+from+Java> It looks fairly
> > > recent, last edit was 20 Sept.
> >
> > That's a really useful page, thanks a lot.
> >
> > One thing -- I don't see generics in there. So, are there other things
> > that I can do in Java that isn't supported (or won't be supported) in
> > Groovy?
>
> Generics are supported.
> At the moment, you can't define anonymous inner classes or nested
> classes.
>
> The page mentioned earlier is a bit outdated and we'll have to update
> it -- for instance the old for loop is supported in Groovy 1.1.
>
> --
> Guillaume Laforge
> Groovy Project Manager
> G2One, Inc. Vice-President Technology
> http://www.g2one.com
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>

--

-- 
Guillaume Laforge
Groovy Project Manager
G2One, Inc. Vice-President Technology
http://www.g2one.com

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

    http://xircles.codehaus.org/manage_email

Re: [groovy-user] Possible to retrieve an exception from Template.make()?

make() doesn't cause the exception as it hasn't written the
template yet just created it. You would normally have:

def t = template.make()
t.writeTo(someWriter) // exception thrown here

As Yegor mentioned, since GROOVY-2186 was fixed
the writeTo throws an exception if one occurs
while trying to perform the writing process.

Paul.

Yegor Bryukhov wrote:
> Should be fixed by now, see
> http://jira.codehaus.org/browse/GROOVY-2186
> 
> On 10/31/07, didge <didge@...> wrote:
>> If something throws an exception within a template, is there a way to catch
>> it so that code executing the template can deal with it?
>>
>> For example,
>>
>>   import groovy.text.*
>>
>>   def ste = new SimpleTemplateEngine()
>>   def template = ste.createTemplate("""
>>   <%
>>     throw new Exception("Catch me somebody, please!")
>>   %>""")
>>
>>   try {
>>     template.make()
>>   }
>>   catch(Exception exc) {
>>     println exc
>>   }
>>
>> Does not catch the thrown exception.  Is there any way that the caller can
>> figure out that the template failed?  Why doesn't make throw the exception
>> or some sort of nested exception?
>>
>> Regards,
>>   didge
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
> 
> 

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

    http://xircles.codehaus.org/manage_email

[groovy-user] Groovy performance patches: testing need

Dear Groovy Users and Developers!

During last several days I commited several performance patches, which
significantly improves my benchmarked tests. Of course, all Groovy
test are passed but changes are so big and serious that additional
testing may help.

If you have cycles and energy to try last Groovy sources on your real
life project and report if you noticed any performance improvements or
any regression it will be highly appreciated. We hope to have RC2
tomorrow and of course would like to know about problems before that.

Best regards
Alex

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

    http://xircles.codehaus.org/manage_email

[groovy-user] Status of the Eclipse Plugin?

Hi.

Currently it is next to impossible to develop Groovy with Eclipse or
NetBeans
due to the immature IDE support provided by the rather experimental state
of the corresponding plugins.

Can someone tell me if it is true that one has to switch to the IDEA IDE to
develop Groovy.

Don't get me wrong: I really do appreciate the work that has been spent on
the
Eclipse plugin, but it is simply unusable for me. It's good to have syntax
coloring,
at least but I couldn't find a way to disable the unusable method completion
when
entering a dot. If one does that or accidently invokes Ctrl-Space Eclipse
tends to
freeze for up to 20-30 secs before the method selection list pops up.
Annoying and
I wonder who uses this 'feature'? If it doesn't work it should be disabled.

Thanks and sorry for complaining but I'd love to be able to gain the
productivity boost
I once got when switching to Eclipse and NetBeans.

Marcus

BTW: Building Groovy classes takes ages and I'm not able to run Groovy code
from within Eclipse...

--

-- 
View this message in context: http://www.nabble.com/Status-of-the-Eclipse-Plugin--tf4730152.html#a13525438
Sent from the groovy - user mailing list archive at Nabble.com.

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

    http://xircles.codehaus.org/manage_email

Re: [groovy-user] Status of the Eclipse Plugin?

Marcus Olk wrote:
> Hi.
>
> Currently it is next to impossible to develop Groovy with Eclipse or
> NetBeans
> due to the immature IDE support provided by the rather experimental state
> of the corresponding plugins.
>
> Can someone tell me if it is true that one has to switch to the IDEA IDE to
> develop Groovy.
>
> Don't get me wrong: I really do appreciate the work that has been spent on
> the
> Eclipse plugin, but it is simply unusable for me. It's good to have syntax
> coloring,
> at least but I couldn't find a way to disable the unusable method completion
> when
> entering a dot. If one does that or accidently invokes Ctrl-Space Eclipse
> tends to
> freeze for up to 20-30 secs before the method selection list pops up.
> Annoying and
> I wonder who uses this 'feature'? If it doesn't work it should be disabled.
>
> Thanks and sorry for complaining but I'd love to be able to gain the
> productivity boost
> I once got when switching to Eclipse and NetBeans.
>
> Marcus
>
> BTW: Building Groovy classes takes ages and I'm not able to run Groovy code
> from within Eclipse...
>
>
>   
I would say that in NetBeans, the Groovy support is slightly beyond the 
experimental stage currently:

http://plugins.netbeans.org/PluginPortal/faces/PluginDetailPage.jsp?pluginid=3914

A lot needs to be done still, but a lot can already be done.

Gj

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

    http://xircles.codehaus.org/manage_email

Re: [groovy-user] Status of the Eclipse Plugin?

get yourself an IDEA 
it surely rocks !

On 11/1/07, Marcus Olk <marcuso@...> wrote:
>
> Hi.
>
> Currently it is next to impossible to develop Groovy with Eclipse or
> NetBeans
> due to the immature IDE support provided by the rather experimental state
> of the corresponding plugins.
>
> Can someone tell me if it is true that one has to switch to the IDEA IDE to
> develop Groovy.
>
> Don't get me wrong: I really do appreciate the work that has been spent on
> the
> Eclipse plugin, but it is simply unusable for me. It's good to have syntax
> coloring,
> at least but I couldn't find a way to disable the unusable method completion
> when
> entering a dot. If one does that or accidently invokes Ctrl-Space Eclipse
> tends to
> freeze for up to 20-30 secs before the method selection list pops up.
> Annoying and
> I wonder who uses this 'feature'? If it doesn't work it should be disabled.
>
> Thanks and sorry for complaining but I'd love to be able to gain the
> productivity boost
> I once got when switching to Eclipse and NetBeans.
>
> Marcus
>
> BTW: Building Groovy classes takes ages and I'm not able to run Groovy code
> from within Eclipse...

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

    http://xircles.codehaus.org/manage_email

Re: [groovy-user] Status of the Eclipse Plugin?

Alex Shneyderman wrote:
> get yourself an IDEA 
> it surely rocks !
>
>   
I agree, from everything I've seen and heard, IDEA is the best when it 
comes to Groovy. 

Gj
> On 11/1/07, Marcus Olk <marcuso@...> wrote:
>   
>> Hi.
>>
>> Currently it is next to impossible to develop Groovy with Eclipse or
>> NetBeans
>> due to the immature IDE support provided by the rather experimental state
>> of the corresponding plugins.
>>
>> Can someone tell me if it is true that one has to switch to the IDEA IDE to
>> develop Groovy.
>>
>> Don't get me wrong: I really do appreciate the work that has been spent on
>> the
>> Eclipse plugin, but it is simply unusable for me. It's good to have syntax
>> coloring,
>> at least but I couldn't find a way to disable the unusable method completion
>> when
>> entering a dot. If one does that or accidently invokes Ctrl-Space Eclipse
>> tends to
>> freeze for up to 20-30 secs before the method selection list pops up.
>> Annoying and
>> I wonder who uses this 'feature'? If it doesn't work it should be disabled.
>>
>> Thanks and sorry for complaining but I'd love to be able to gain the
>> productivity boost
>> I once got when switching to Eclipse and NetBeans.
>>
>> Marcus
>>
>> BTW: Building Groovy classes takes ages and I'm not able to run Groovy code
>> from within Eclipse...
>>     
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>   

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

    http://xircles.codehaus.org/manage_email

RE: [groovy-user] Groovy performance patches: testing need

Should we be expecting a very short cycle on RC3 then?  

Jason Smith

-----Original Message-----
From: Alex Tkachman [mailto:alex.tkachman@...] 
Sent: Thursday, November 01, 2007 3:13 AM
To: dev@...; user@...
Subject: [groovy-user] Groovy performance patches: testing need

Dear Groovy Users and Developers!

During last several days I commited several performance patches, which
significantly improves my benchmarked tests. Of course, all Groovy test
are passed but changes are so big and serious that additional testing
may help.

If you have cycles and energy to try last Groovy sources on your real
life project and report if you noticed any performance improvements or
any regression it will be highly appreciated. We hope to have RC2
tomorrow and of course would like to know about problems before that.

Best regards
Alex

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

    http://xircles.codehaus.org/manage_email