gmane.comp.lang.groovy.jsr

Groovy 1.5.6 is out!

Guillaume Laforge — 2008-04-25T18:21:20

Hi all, G2One and the Groovy development team is pleased to announce the release of Groovy 1.5.6, a bug fix release for the stable Groovy 1.5.x branch. A regression introduced in 1.5.5 was fixed, and 35 bugs have been resolved (generics, MOP, and joint compiler issues, better line information for IDE support, etc) As usual, you can download the latest Groovy dustribution here: http://groovy.codehaus.org/Download And read the change log to know all the details there: http://jira.codehaus.org/browse/GROOVY?report=com.atlassian.jira.plugin.system.project:changelog-panel Enjoy!

Fwd: final Groovy JSR?

Guillaume Laforge — 2008-04-05T17:10:29

Wasn't delivered. ---------- Forwarded message ---------- From: Bill Shannon public.gmane.org> Date: Sat, Apr 5, 2008 at 12:40 AM Subject: Re: final Groovy JSR? To: Guillaume Laforge public.gmane.org> Cc: jsr-241-comments-vP450+ZD9pU< at >public.gmane.org, Groovy JSR public.gmane.org> Guillaume Laforge wrote: But what if the library is compiled by Foo's Groovy compiler and my program using the library is compiled by Bar's Groovy compiler? You have to decide whether this is important and/or likely. I agree you can probably ignore this for the first version. Will this get any easier in Java SE 7 with the new dynamic language bytecode?

Fwd: final Groovy JSR?

Guillaume Laforge — 2008-04-05T17:10:13

Wasn't delivered. ---------- Forwarded message ---------- From: Bill Shannon public.gmane.org> Date: Fri, Apr 4, 2008 at 11:59 PM Subject: Re: final Groovy JSR? To: Guillaume Laforge public.gmane.org> Cc: jsr-241-comments-vP450+ZD9pU< at >public.gmane.org, Groovy JSR public.gmane.org> Guillaume Laforge wrote: Yes, exactly. I think it would be better if you did, but it's up to you to decide. You're allowed to make that choice. It's up to your expert group to decide whether that's a good choice. Personally, I think this might be acceptable for a first release, but long term it will limit acceptance of Groovy. But you should work through the scenarios for how you expect people to use Groovy to see if it will be an issue for you. For example, do you expect people to write libraries using Groovy, which they would distribute as jar files? We include them in the TCK User's Guide. Let me f

Re: final Groovy JSR?

Guillaume Laforge — 2008-04-04T22:33:42

Yes, for sure, conceptually speaking, this would be desired. For Java, this is simpler as a call to a method is directly encoded in the bytecode. No intermediary layer of indirection. It then just depends on the runtime part (JDK classes, third party libraries, etc) But for a dynamic language, in the bytecode you'll find some calls to utility classes handling the double dispatch. Some of them are public APIs (which will be part of the JSR), but others may be present that are specific to each implementation. So we'll have to think deeper as to what we really want to make portable or not. Tricky issue :-) Right. This has always been possible (as long as you have the Groovy runtime on your classpath). We can seamlessly integrate with Java, or any other alternative language for the JVM. But the problem comes when we have to be compatible between different implementations of Groovy. At the basic object level, things are just fine, but it's when you get into metaprogramming techniques that this may be more prob

Re: final Groovy JSR?

Guillaume Laforge — 2008-04-04T21:41:04

Bonjour Liz, On Wed, Mar 26, 2008 at 11:37 AM, Liz M Kiener public.gmane.org> wrote: Alright, I saw it. It'll take me some time to get the EDR finished, and it won't be before JavaOne. Yes. Yup, I saw that, this is handy. Merci beaucoup :-)

Re: final Groovy JSR?

Guillaume Laforge — 2008-04-04T21:38:18

Hi Bill, Thanks a lot for your explanations. I haven't been able to answer earlier, I'm sorry. Some comments inline. On Sat, Mar 22, 2008 at 8:24 PM, Bill Shannon public.gmane.org> wrote: What do you mean by language/compiler portion, and runtime portion exactly? I just want to be sure I understood correctly. For the language part, we need to explain the semantics of the language, its grammar, etc. For the runtime part, you mean things like the libraries? ie. a closure class, a GString class, etc. Is that what you meant? Okay, it's up to us to decide the level of integration the spec mandates or not for a language to be considered a valid Groovy implementation. Furthermore the TCK will help ensure this. Ok, that makes perfect sense. Back on the level of integration mentioned above, and on this portability / interoperability aspect, Groovy mandates a seamless integration with Java. But does it mean we'd also mandate a perfect interoperability with other Groovy implementatio

Re: final Groovy JSR?

Guillaume Laforge — 2008-03-22T13:46:48

Hello Bill, On Fri, Mar 21, 2008 at 7:25 PM, Bill Shannon public.gmane.org> wrote: Very good question. Actually, after a long period of hibernation on the JSR front, we're resuming work on it in the upcoming months. But we'd be happy to have some guidance to the steps to follow, and details of the key deliverables that are expected to ship with the JSR. So far, the RI is there, of course, in the shape of Groovy 1.5.4. The TCK is not split from the Groovy test suites, so we'd need to find an easy way for people to reuse it if they want to develop a compatible Groovy language. On the spec side, we have the language grammar in an EBNF and diagram form, but what is still missing is the writing of the formal specification document, beyond our online documentation or the books we've written on the topic.

Re: [groovy-dev] Tentative Roadmap

Guillaume Laforge — 2007-12-17T09:40:39

On Dec 17, 2007 10:25 AM, Alexandru Popescu ☀ gmail.com> wrote: You're welcome :-) At least, it's not in contradiction with the roadmap! Agreed, this is what the 1.5.x releases are for. It's going to be a long process I suspect, as various experiments will have to be done, lots of discussions, a nice general proposal of what we really want, etc. So it's something that is going to be done in parallel to the progress we make in 1.x. I tried to put certain features at certain milestones, but we can certainly reorder the priorities. I've put multiple assignments early in the roadmap because we had promised them in 1.1/1.5, but as they're certainly not critical, we can postpone them to a latter release, it's not really critical. In the new features, there are things which should be discussed for inclusion or not. For instance, anonymous inner classes, nested classes and co. Initially, in the early days of Groovy, we didn't want to support them because we found them ugly, and

Tentative Roadmap

Guillaume Laforge — 2007-12-16T23:50:06

Dear Groovy developers, Now that we have released 1.5, it is time to think about the future of Groovy, by discussing its roadmap. After some discussions at GDC#4 ( http://docs.codehaus.org/display/GroovyJSR/GDC4+Discussions), on the lists, and elsewhere, we've listed possible improvements and new features. Jochen and myself compiled a tentative roadmap this weekend, taking these ideas into account and trying to lay them out across potential release numbers. This is a tentative roadmap. Certain features can be discussed, whether we do want them or not. And there's room for moving features from one to another release. New ideas missing can also be introduced. So it's still pretty open at the moment. Note that the roadmap can change across the course of time according to the progress (or lack thereof) we make on the GEPs (Groovy Extension Proposals). It is not set in stone today, even after our upcoming discussions. The GEPs will drive us through the releases. It is very important that we try to clearly de

What's new in Groovy 1.5?

Guillaume Laforge — 2007-12-09T15:26:27

Hi all, After the announcement of the release of Groovy 1.5, as promised in the release notes, here's a detailed article on what's new in Groovy 1.5. Read it on InfoQ: http://www.infoq.com/articles/groovy-1.5-new

Groovy 1.5 is there!

Guillaume Laforge — 2007-12-07T23:41:12

Hi all, I'm very pleased to announce the release of Groovy 1.5. You can read the release notes there: http://docs.codehaus.org/display/GROOVY/2007/12/07/Groovy+1.5+released An upcoming article on InfoQ will give you a more in-depth overview of this new version. Thanks a lot to everybody: developers, contributors, users. Without you, Groovy wouldn't be the great dynamic language it is today.

Release candidate 2 is available!

Guillaume Laforge — 2007-11-02T19:13:20

Dear all, The Groovy development team and G2One , the Groovy & Grails company, are happy to announce the new milestone of Groovy: the second release candidate is here. Just a few weeks after the first release candidate, this new version focused mainly on bug fixing, ironing out the Swing console with a nice new icon toolbar and the interactive shell, and the XML handling. You can have a closer look at the JIRA issuesfor more detailed information and you can download Groovy 1.1-rc-2 from the usual place. Apart from these bugs and little improvements, we kept on increasing the performance of Groovy. As an informal benckmark, we measured the time taken by our test suites to run, and for instance, according to the Grails team, the Grails test suites executed about 40% faster with Groovy 1.1-rc-2 than with Groovy 1.1-rc-1, of course, depending on your project

Groovy 1.1-beta-3 released, RC-1 and 1.1-final around the corner

Guillaume Laforge — 2007-09-20T23:47:19

Dear Groovy friends, I've blogged about the new here: http://glaforge.free.fr/weblog/index.php?itemid=222&catid=2 and there: http://docs.codehaus.org/display/GROOVY/2007/09/20/Groovy+1.1-beta-3+released%2C+RC-1+and+1.1-final+around+the+corner But here it is: Groovy 1.1-beta-3 is there, paving the way for an RC-1 in the following weeks, and if all goes well, for 1.1-final in October, right in time for the Grails eXchange conference that takes place in London. This conference will also be the opportunity for the Groovy developer team to meet for the fourth Groovy Developer Conference! With Groovy 1.1 released by then, it'll be time to think about what's going to happen for the next major version of Groovy. Before going through the new release, let me recap some of the nice things that have been happening lately around Groovy: * JetBrains released a second milestone to the wonderful Groovy & Grails IntelliJ IDEA plugin, so be sure to check it out, as you'll feel at ease developing Groovy with all the

how to make new specification request.

amr_qura — 2007-08-18T19:33:43

i'm working in web application projects using JSF . i'm asked from team manager to write "module specification request" for every web module. can anybody tell me what the content of any specification request document.

how to maike

amr_qura — 2007-08-18T19:31:01

get scripting engine by file extension

Anton Arhipov — 2007-07-30T21:30:05

Hello! I have an application where I use JSR-223 for evaluating the scripts, and I use file extension for identifying the scripting engine that is required to evaluate the script: ScriptEngineManager scriptEngineManager = new ScriptEngineManager(); ScriptEngine engine = scriptEngineManager.getEngineByExtension("groovy"); With groovy-1.0 it works fine. but with groovy-1.1-beta2 this code throws a following exception: Exception in thread "main" java.lang.IncompatibleClassChangeError: Found interface groovy.lang.MetaClass, but class was expected at com.sun.script.groovy.GroovyScriptEngine.( GroovyScriptEngine.java:63) at com.sun.script.groovy.GroovyScriptEngineFactory.getScriptEngine( GroovyScriptEngineFactory.java:87) at javax.script.ScriptEngineManager.getEngineByExtension( ScriptEngineManager.java:275) at And in the version 1.0 there really was "public abstract class MetaClass" which is now "public interface MetaClass extends MetaObjectProtocol"

Groovy 1.1-beta-2 released!

Guillaume Laforge — 2007-07-05T21:36:10

Dear community, The Groovy team is pleased to announce the release of Groovy 1.1-beta-2, yet another step on our aggressive roadmap towards the release of Groovy 1.1 in October. For this release, I would like especially to highlight two key contributions to the project: * First of all, after we've added Java 5 annotation support in Groovy 1.1-beta-1, this time, it was generics' turn. Thanks to the help of some JBoss developers who've integrated Groovy in JBoss Seam, we've been able to test our support for annotations and generics, and to make sure we would release a quality milestone to our users. Groovy is the first alternative dynamic language for the JVM that supports annotations and generics, so that you can integrate Groovy with any Enterprise application frameworks like EJB 3 / JPA, JBoss Seam, Google Guice, Spring, etc. * Secondly, I'm very happy to report the contribution of JetBrains to the development of Groovy. While working on the IntelliJ IDEA plugin for Groovy and Grails, the talentu

Groovy 1.1-beta-1 released with annotation support

Guillaume Laforge — 2007-04-30T22:16:38

Dear all, After Groovy was awarded the first prize of the JAX conferencein Germany last week for being the *most innovative and creative project in 2007 in the Java community*, we're pleased to announce the *release of Groovy 1.1-beta-1*. This release is the first beta release after the release of Groovy 1.0. But it's a very important release as we've been working on key features putting Groovy clearly as the *de facto enterprise scripting solution*. Indeed, Groovy is now the first and sole alternative language for the JVM that *supports Java 5 annotations*. Groovy 1.1-beta-1 also supports Java 5 *static imports*. You can now use Groovy to write your EJB 3 / JPA beans, to wire your components with Google Guice, to mark your services transactional

Re: Fwd: JavaOne EG Meeting Room

Jeremy Rayner — 2007-03-23T11:06:56

Will there be any conference phone facilities, as I'll be in the UK that day Jez.

RE: Fwd: JavaOne EG Meeting Room

Dierk Koenig — 2007-03-23T10:36:19

I'll be there and happy to meet everybody. Guillaume, I guess I'm not yet an official member of the JSR expert group. Would you mind promoting me so? ;-) cheers Dierk --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email

Fwd: JavaOne EG Meeting Room

Guillaume Laforge — 2007-03-22T06:56:31

For those who will be at JavaOne this year (Groovy / Grails developers and JSR EG members), we might have a room to make a quick meeting at the Argent hotel if needs be. ---------- Forwarded message ---------- From: Liz M Kiener public.gmane.org> Date: Mar 22, 2007 6:36 AM Subject: JavaOne EG Meeting Room To: SPECLEADS-vP450+ZD9pU< at >public.gmane.org Hello All - The PMO is pleased to offer you once more this year a room at the Argent Hotel for EG meetings during JavaOne. The room will be available all week until Fri 11 May on a first come first served basis. You can schedule the room by sending me email with date and time you would like. Kind regards, Liz :-)