Yes, finally out. Lots of bug fixes and improvements including:

* BOO-224 - partial classes
* BOO-597 - extension methods
* BOO-610 - Optional return on inline closures.
* BOO-408 - Explode operator not exploding when using overloaded methods
* BOO-527 - Make .pdb files work under .NET 1.1 and .NET 2.0
* BOO-567 - emit debug info for separate files
* BOO-534 - BeginInvoke overloads are not valid on ms.net 2.0
* BOO-540 - Unable to call blank constructor on a ValueType
* BOO-579 - line numbers off in wsaboo

The complete list is here

Thanks to everyone on the boo community specially to the people on #boo and more specially so to those that contributed patches, comments and/or ideas that got into this release:

* Arron Washington
* Ayende Rahien
* Cameron Kenneth Knight
* Daniel Grunwald
* Doug Holton
* Fábio Batista
* Michael Sloan
* Peter Johanson
* Scott Fleckenstein
* Sorin Ionescu
* Steve Donovan

Special mention for Daniel Grunwald's work on the #develop 2.0 addin. If you haven't checked it out yet, do it and be amazed.

As usual download it from here.

Yan Container 0.7 is released.

This release includes a sub-project for XML configuration called Nuts.

Nuts is a modular xml dialect of Yan with support of flexible component combinations and extensible xml tags.

A Spring integration package is also included to allow Spring beans and FactoryBeans to be used inside Nuts. This enables Nuts to take advantage of various services provided by Spring such as AOP.

Please refer to Nuts for detailed information.

Yan v0.7 can be downloaded here

Just before the Groovy / JSR-241 meeting happening in Paris at the end
of the week, the Groovy team decided to roll a new version! We're delighted to
announce the release of Groovy JSR 04.

First of all, a big work has been done to improve the compilation
process and the class loading mechanism. Groovy had problems compiling
classes with circular references and with script dependencies.
Moreover, some imports of inner classes weren't resolved correctly. As
those changes are important, those of you embedding Groovy in their
applications might face some potential problems. So if you're in that
case and are affected with the changes, please tell us how it goes and
report JIRA issues with detailed explanations of your integration
scenario. Thanks in advance for that, and sorry for any inconvenience.

The startup scripts have been improved, and we have replaced
clasworlds with a custom implementation. This time, we hope the
line-endings of the scripts are fixed correctly. On Windows, we can
eventually use more than 8 parameters on the command-line, and you
should be able to safely use paths with spaces in them. You can now
customize the classpath more easily with the -cp flag.

We've upgraded the dependencies on ASM from 2.0 to 2.1. But you can
still use the groovy-all-*.jar to escape from jar hell in case you
already need those jars on your classpath of your application.

Some work was done on the groovy and groovyc Ant tasks. You can now
use a debug flag to see what's happening under the hood. And the
interaction with Maven 1.0.2 and 1.1 should be nicer when the tasks
are reused in that context.

On the bytecode generation front, we've properly implemented the
support for synchronized blocks. We've also fixed some missing line
information, so that stacktraces are as helpful as possible while
debugging.

Regarding builders, you can now use quoted method names, so that
you're able to use hyphens or colons in tags. The support for
namespaces has also been improved, and you should be able to spice up
your GPath expressions and be able to use our parsers and slurpers on
namespaced XML stanzas.

A few bugs were fixed with scoping inside closures and nested closures.

The two main aspects remaining for Groovy to reach its 1.0 final
milestone is to clarify the name resolution and scoping rules. Those
two concerns will hopefully be addressed during the Groovy JSR
meeting, and we're going to implement these rules as quickly and as
thouroughly as possible. Keep in mind that those rules might be a
little different than our current rules. However, we hope these rules
will be more coherent and closer to what we're used to in Java.

The Groovy team and myself are looking forward to hearing about your
feedback regarding this new release which should bring even more
maturity to our Groovy world. We're getting close to the finish line.
And this project would be nowhere without you all, users, developers,
affictionados... Thanks a lot for your support, your enthousiasm and
your work towards our 1.0 goal.

As usual, you'll find the distributions on our download pages

--
Guillaume Laforge
Groovy Project Manager

We are pleased to announce the ServiceMix 2.0 Release. New features include...

* Improved JBI support including both interface based routing as well as service based routing together with improved WSDL parsing
* Support for Publish and Subscribe Routing
* Improved JAX WS support
* Migration to XBean as the XML configuration mechanism which works with any Spring release and allows us to mix and match ServiceMix configuration with other XML configuration mechanisms like ActiveMQ and Jencks
* Migration to backport.util.concurrent to make it easier to move direct to a pure Java 5 solution.
* a new Loan Broker example from the EIP Patterns Book
* a new simpler POJO based deployment model
* build reorganised to make ServiceMix more modular
* a new ChainedComponent which implements simple pipelines of components easily

Enjoy!