<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://blog.gmane.org/gmane.comp.lang.groovy.devel">
    <title>gmane.comp.lang.groovy.devel</title>
    <link>http://blog.gmane.org/gmane.comp.lang.groovy.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19802"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19791"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19786"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19780"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19774"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19771"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19767"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19760"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19748"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19747"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19745"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19724"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19709"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19701"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19696"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19692"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19684"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19669"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19656"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19648"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19802">
    <title>[groovy-dev] Whither ModelBinding?</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19802</link>
    <description>I notice org.codehaus.groovy.ModelBinding has been removed in 1.6.

What is the point of this?  It is a breaking change for applications 
that used groovy.ui.* as a model for correct Groovy usage.

I've tested and find that the 1.5.x works fine in 1.6.  If the intention 
is to deprecate it, then it should be annotated not removed.

Jim


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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Jim White</dc:creator>
    <dc:date>2008-11-29T19:25:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19791">
    <title>[groovy-dev] Shouldn't generated getter/setter methods be flagged as synthetic?</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19791</link>
    <description>This is something of a follow-up to "Re: [groovy-user] 
Class.getDeclaredMethods - not very nice behaviour".

I see that most of the methods and apparently all of the fields 
generated by Groovy are marked as synthetic, with the exception of the 
generated getters and setters.  I've opened a JIRA with a detailed view.

http://jira.codehaus.org/browse/GROOVY-3174

Also there's a related issue in which some new and clearly synthetic 
fields are not getting marked as synthetic.

http://jira.codehaus.org/browse/GROOVY-3175

Jim


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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Jim White</dc:creator>
    <dc:date>2008-11-29T04:00:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19786">
    <title>[groovy-dev] Safe to delete AsmClassGenerator#isNonStaticField?</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19786</link>
    <description>
Does anyone know of any usages of:

protected boolean isNonStaticField(Expression expression)

within AsmClassGenerator?

We don't use it in our codebase and I suspect it is left over from
an earlier refactoring but it is possible though not likely that
some other codebase could be relying on it.

Anyone remember the history?

Paul.

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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Paul King</dc:creator>
    <dc:date>2008-11-29T01:58:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19780">
    <title>[groovy-dev] I am seeing line number weirdness</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19780</link>
    <description>In the Gant tests I have a situation where a Gant script should result
in an error message with the line number of the Gant script reported.
Groovy 1.5.x reports line number 1 always even though the line number of
the script is 6.  Groovy 1.6.x reports the correct line number of 6.
Trunk used to report 6 but something has changed in the last 5 weeks and
now it too reports 1 always.  The inference is that newlines are being
treated as space and not counted when a script is evaluated in a Groovy
Shell.

Before creating an example of the problem, I thought I would check to
see if this was in fact a known problem.

Thanks.
  
</description>
    <dc:creator>Russel Winder</dc:creator>
    <dc:date>2008-11-28T19:20:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19774">
    <title>[groovy-dev] Resolved vs Closed</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19774</link>
    <description>Hi gang!

What's the difference/dev policy on "Closed" vs "Resolved" in JIRA?

I see this:

http://www.nabble.com/JIRA:-%22closed%22-vs-%22resolved%22-td13351086.html

Which suggests we should be using resolved for issues that have been 
accepted and fixed.

Ah, there's this:

http://www.atlassian.com/software/jira/docs/latest/default_workflow.html

The key idea here is that the person that fixes/implements an issue 
marks it resolved.  Once others have done sufficient testing that there 
is consensus that the issue is indeed resolved then it gets closed.  But 
certainly we shouldn't be hitting "closed" simply because a change has 
been committed.

Jim


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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Jim White</dc:creator>
    <dc:date>2008-11-27T18:05:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19771">
    <title>[groovy-dev] [GroovyWS] WSClient needs refactoring, some short ideas</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19771</link>
    <description>Hello everybody.
First of all I’d like to thank all contributors for realizing GroovyWS. It allows some nice techniques. ;) Now the time is come to give something back. I looked into the sources (unfortunately only 0.3) and realized that some refactoring could be done (which already took part in 0.4).

To shorten the whole story I made a short list with some ideas. Perhaps some of the points could be discussed here to see if they could be implemented.

- Add interface (create, invoke)
- Add abstract CXFClient
- Subtype WSClient
- Add abstract logMethod
- Add overridable createClient() (in order to set a own factory, e.g. subclass of the DynamicFactory)
- Check method’s visibilities
- Extract key of maps into constants or enum-types
- HandleResponse-method in order to define the result-type as desired.

Best regards,
Dennis.

PS: I attached some classes of a quick refactoring which I started with 0.3 in order to getting an idea of the points I listed.

</description>
    <dc:creator>groovy.mailing-Mmb7MZpHnFY&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2008-11-27T07:52:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19767">
    <title>[groovy-dev] My rating impugned!</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19767</link>
    <description>Of all the things to knock down my batting average:

http://bamboo.ci.codehaus.org/browse/GROOVY-CORE15-3770

I guess the consolation is that it could happen to anyone...

Jim


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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Jim White</dc:creator>
    <dc:date>2008-11-25T06:56:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19760">
    <title>[groovy-dev] information in nullpointerexception</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19760</link>
    <description>Hi, I noticed that a while back Groovy used to add helpful information to
the message field of a NullPointerException, like "cannot get property: x on
null object".  In the code it looks like this was commented out when moving
from the Invoker to the InvokerHelper class. Was it meant to be left
commented out, or can that be "reactivated"?
</description>
    <dc:creator>kris helenek</dc:creator>
    <dc:date>2008-11-24T19:19:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19748">
    <title>[groovy-dev] GroovyConsole broken in retro build</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19748</link>
    <description>
When tracking down why the build broke on 1.4 (I think it is an old bug
to do with XML namespace handling on old jdks) I tried to fire up the
GroovyConsole under the retro build. It fails with this error:

Caused by: java.lang.Error: Do not use javax.swing.JFrame.add() use javax.swing.JFrame.getContentPane().add() instead

traced back to here:

   at javax.swing.JFrame.createRootPaneException(JFrame.java:465)
   at javax.swing.JFrame.addImpl(JFrame.java:491)
   at java.awt.Container.add(Container.java:307)
   ...
   at groovy.swing.factory.WidgetFactory.setChild(WidgetFactory.groovy:57)

Looking at WidgetFactory, it is indeed an add as per the error message:

   parent.add(child)

Does the suggestion in the error message make sense?

This doesn't appear to be a problem on 1.5+

Cheers, Paul.


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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Paul King</dc:creator>
    <dc:date>2008-11-23T00:55:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19747">
    <title>[groovy-dev] Showstopper of a bug</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19747</link>
    <description>Lest anyone has been feeling a bit complacent about the potential for 
serious Groovy 1.6 bugs for fundamental behavior, what with the size of 
the test suite and applications such as Grails and all, check out 
GROOVY-3165.

Given something like:

char[] ca = new char[1]

assignments of the form:

ca[0] = 'a'

fail with a ClassCastException!

http://jira.codehaus.org/browse/GROOVY-3165

Also I've not heard whether anyone has checked out the bug with super I 
reported earlier this week.

http://jira.codehaus.org/browse/GROOVY-3163

That makes three significant bugs turned up from trying to run one 
fairly small application (IFCX Wings).  I wonder whether folks 
downstream are really taking the need to report problems with the RCs 
seriously enough.

And I haven't even had a chance yet to look into how the change with 
regex works...

Jim


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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Jim White</dc:creator>
    <dc:date>2008-11-22T23:46:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19745">
    <title>[groovy-dev] Bring miscellaneous small changes from 1.6 into 1.5.</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19745</link>
    <description>I've noticed a number of small changes that have been put into the 1.6 
branch that haven't made it into 1.5.  I've opened a JIRA about cleaning 
some of that up and it includes a patch for my proposed merge for DGM. 
As for motivation; In addition to keeping implementation/features 
aligned as much as possible, I also like to keep the diffs as clean as 
possible.

http://jira.codehaus.org/browse/GROOVY-3164

If there are no objections I'll do the merge in the next day or so.  If 
there are other files that should get this treatment, then please do 
nominate them (or better yet, clean 'em up!).

Jim


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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Jim White</dc:creator>
    <dc:date>2008-11-22T01:39:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19724">
    <title>[groovy-dev] Add DGM.minus(Date, Date) to 1.6?</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19724</link>
    <description>Anyone object?

http://jira.codehaus.org/browse/GROOVY-3162

Jim


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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Jim White</dc:creator>
    <dc:date>2008-11-21T00:43:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19709">
    <title>[groovy-dev] Problem with Groovy Console on trunk</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19709</link>
    <description>Hi,

I was trying to run Groovy Console on Mac OS X, and got the below stacktrace.
I launched it from within IntelliJ IDEA, but I don't think it matter.

Exception in thread "main" groovy.lang.MissingPropertyException: No
such property: visualizeScriptResults for class:
groovy.ui.view.MacOSXMenuBar
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:49)
at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:240)
at groovy.ui.view.MacOSXMenuBar$_run_closure1_closure4.doCall(MacOSXMenuBar.groovy:79)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.groovy.reflection.Cach</description>
    <dc:creator>Guillaume Laforge</dc:creator>
    <dc:date>2008-11-20T15:25:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19701">
    <title>[groovy-dev] GroovyConsole broken on trunk?</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19701</link>
    <description>
I am getting:

No signature of method: java.awt.Dimension.minus() is applicable for argument types: (java.lang.Integer) values: {1}

when trying to start up the GroovyConsole on trunk on windows. The stack trace also shows:

groovy.ui.Console.getLastResult(Console.groovy:104)

Anyone else seeing this or is it something local?

Thanks, Paul.

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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Paul King</dc:creator>
    <dc:date>2008-11-19T13:08:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19696">
    <title>[groovy-dev] Groovy Support in Apache Sling</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19696</link>
    <description>Hi all,

Paul King pointed us at Apache Sling [1] to the integration of JSR-223
support in the recent Groovy 1.7 beta1 SNAPSHOT [2].

This is actually good and cool stuff in itself. Adding the required OSGi
manifest headers is simple (see the sample Maven 2 POM at [3]).

Now, I am wondering, whether it would not make more sense to actually
also include the OSGi bundle headers into the groovy-all.jar to be able
to deploy the JAR file as an OSGi bundle directly into the OSGi framework ?

WDYT ?

Thanks and Regards
Felix


[1] http://incubator.apache.org/sling/
[2]
https://issues.apache.org/jira/browse/SLING-315?focusedCommentId=12648585#action_12648585
[3] https://issues.apache.org/jira/secure/attachment/12394227/pom.xml

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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Felix Meschberger</dc:creator>
    <dc:date>2008-11-19T07:48:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19692">
    <title>[groovy-dev] Ivy bumped to 2.0.0-rc2</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19692</link>
    <description>pom.xml in trunk and 1.6 entry for Apache Ivy bumped to 2.0.0-rc2.

Jim


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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Jim White</dc:creator>
    <dc:date>2008-11-18T20:43:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19684">
    <title>[groovy-dev] Bamboo agent stuck</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19684</link>
    <description>Who do we report the stuck agent in Bamboo?  The build for "Cargo - 
Trunks (Maven2) on JDK 1.4" is coming up on 100 hours of build time and 
obviously isn't going to finish.  The "Support" and "Contact 
Administrator" pages don't seem too helpful.

Jim


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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Jim White</dc:creator>
    <dc:date>2008-11-18T17:51:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19669">
    <title>[groovy-dev] Groovy's .with {} - a toy?</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19669</link>
    <description>
I like alot of things about Groovy, and "with" seems like a nice thing to
have, but I'm bothered by the fact that it currently seems have a toy
implementation.  Consider:

 class Foo {
    def add(x) {
        println "wrong add: $x"
    }

    def doit(x) {
        def n = [1,2,3]
       
        n.with {
          add(x)
          each { println it }
        }
       
        println n
    }

    def test() {
        doit("before")
    }
}

new Foo().test()

wrong add: before
Foo$_doit_closure1&lt; at &gt;f3724c
[1, 2, 3]

(tried w/Groovy 1.5.6 and 1.6.0-beta2)

The first call in the with closure (add) is goes not to the list, but to the
add in the owner scope. This shows me that using "with" leaves me open to
inadvertent breakage in the future if I happen to add a method with the
"wrong" name to a class that uses a with clause in a completely different
method.  This could be addressed if the with implementation changed the
dispatch order of its closure to DELEGATE_ONLY or DELEGATE_FIRST.  I would
suggest based on t</description>
    <dc:creator>rafial</dc:creator>
    <dc:date>2008-11-18T06:51:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19656">
    <title>[groovy-dev] Compiler class loading strategy</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19656</link>
    <description>
Hi,

I finally have a working solution to the problems discussed here:
http://www.nabble.com/-GMaven--Global-transforms-don%27t-get-picked-up-to20285746.html

The solution is based on a new class loading strategy that:
- avoids pollution of the compile classpath (no more need to fork the
compiler to accomplish this)
- avoids version conflicts for libraries used both by compiler and
application to be compiled
- makes it possible to compile against other Groovy versions (once the
compiler supports this)
- is non-invasive because it is only used by selected compiler clients (e.g.
FileSystemCompiler); all other clients remain unaffected
- makes transforms work under GMaven

The Groovy 1.6 branch builds successfully with the new class loading
strategy in place (including tests). I'll post a patch in a day or two.
Hopefully you'll be able to make something out of it.

Cheers,
Peter






</description>
    <dc:creator>Peter Niederwieser</dc:creator>
    <dc:date>2008-11-17T00:43:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19648">
    <title>[groovy-dev] Groovy-2849 - Issue also exists for method calls</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19648</link>
    <description>Hi,
The issue Groovy-2849 is reported for property access within nested
closures.

I have modified AsmClassGenerator a bit to fix the reported issue (1.5.8/
1.6 RC1/ 1.7-beta1) and attached the patches on JIRA.

The same issue is also there for method calls, as show in the testcase
below. Should a separate JIRA be opened for it and is it ok to fix it under
Groovy-2849 itself?

rgds,
Roshan
--------------------------------------------
class Groovy2849Bug extends GroovyTestCase {
    def void testGroovy2849BugForMethodCall(){
        def testObj = new Groovy2849Method()
        assert testObj.c1() == "m[Groovy2849]"
    }
}

class Groovy2849Method {
    def m(){return "m[Groovy2849Method]"}
    def c1 = {
        def m = {return "m[Groovy2849Method-&gt;Closure1]"}
        def c2 = {
            /*
             *  If both 'm()' and 'this.m()' are used as follows,
             *  'this.m()' should not resolve to c1 closure's 'm()' method
call.
             *  It should resolve to outermost Groovy2849Method's 'm()'.</description>
    <dc:creator>Roshan Dawrani</dc:creator>
    <dc:date>2008-11-16T09:21:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.lang.groovy.devel/19646">
    <title>[groovy-dev] Groovy For OpenOffice is a Sun CIP award winner!</title>
    <link>http://comments.gmane.org/gmane.comp.lang.groovy.devel/19646</link>
    <description>Howdy gang.

The recent discussion on groovy-dev about JSR-223 prompts me to make the 
belated announcement that my IFCX Groovy For OpenOffice (G4OO) extension 
is a Silver Award winner in the Sun OpenOffice.org Community Innovation 
Program (CIP).

http://development.openoffice.org/awardees-2008.html

Groovy For OpenOffice adds the ability to implement OpenOffice macros in 
Groovy.  It also includes Apache Ivy, the agile dependency manager, so 
that macros can easily use any additional JARs they might need.

http://www.ifcx.org/

It's raison d'etre is IFCX Wings, a literate scripting tool that enables 
any language with a JSR-223 Scripting Engine to be used "live" within 
OpenOffice documents.

I expect future development of G4OO to lead to eventual inclusion of 
JSR-223 support (and probably BSF as well) into OpenOffice.

Jim


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

    http://xircles.codehaus.org/manage_email



</description>
    <dc:creator>Jim White</dc:creator>
    <dc:date>2008-11-15T18:23:32</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.lang.groovy.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.lang.groovy.devel</link>
  </textinput>
</rdf:RDF>
