Preparing For Grails 2.0.1

[Jeff Brown-4]

We would like to issue a code freeze on the 2.0.x branch around COB today  Because we have the weekend between today and when the release will be built we don't really need to nail down a specific timezone but if you have pending changes, please try to get them in today.

If you have any questions or concerns about the release, please speak up.

Thanks to all who have helped with the release!



jb

--
Jeff Brown
[hidden email]
SpringSource - A Division Of VMware
http://www.springsource.com/

Autism Strikes 1 in 166
Find The Cause ~ Find The Cure
http://www.autismspeaks.org/


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

    http://xircles.codehaus.org/manage_email

[Robert Fletcher-2]

Is it too late for my fix for GRAILS-8436 to get in? Sorry about being
down to the wire. There's a pull request here:
https://github.com/SpringSource/grails-data-mapping/pull/24

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

    http://xircles.codehaus.org/manage_email

[bobbywarner]

The update to Groovy 1.8.6 was missed in two places.  Obviously dependencies.txt doesn't really matter, but build.properties probably does, right?  Just sending an email in case there's any impact of having 1.8.5 in build.properties when it should be 1.8.6 for the upcoming Grails 2.0.1 release.

Here's my pull request:
https://github.com/grails/grails-core/pull/162


Thanks,
Bobby

[rosenfeld]

Em 10-02-2012 14:52, Jeff Brown-4 [via Grails] escreveu:

We would like to issue a code freeze on the 2.0.x branch around COB today  Because we have the weekend between today and when the release will be built we don't really need to nail down a specific timezone but if you have pending changes, please try to get them in today.

If you have any questions or concerns about the release, please speak up.

I do have. It broke both mongo and mongo-morphia plugins for my applications:

http://grails.1312388.n4.nabble.com/Blocker-bug-for-Grails-2-0-1-no-Mongo-plugin-mongo-or-mongo-morphia-works-tt4384268.html

Rodrigo

[rosenfeld]

Em 13-02-2012 14:49, rosenfeld [via Grails] escreveu:

Em 10-02-2012 14:52, Jeff Brown-4 [via Grails] escreveu:

We would like to issue a code freeze on the 2.0.x branch around COB today  Because we have the weekend between today and when the release will be built we don't really need to nail down a specific timezone but if you have pending changes, please try to get them in today.

If you have any questions or concerns about the release, please speak up.

I do have. It broke both mongo and mongo-morphia plugins for my applications:

http://grails.1312388.n4.nabble.com/Blocker-bug-for-Grails-2-0-1-no-Mongo-plugin-mongo-or-mongo-morphia-works-tt4384268.html

Just as an update, it also break my unit tests with the same error messages, even after removing any MongoDB plugins, although the application itself will work fine.

Rodrigo.

[rosenfeld]

Em 13-02-2012 15:48, rosenfeld [via Grails] escreveu:

Em 13-02-2012 14:49, rosenfeld [via Grails] escreveu:

Em 10-02-2012 14:52, Jeff Brown-4 [via Grails] escreveu:

We would like to issue a code freeze on the 2.0.x branch around COB today  Because we have the weekend between today and when the release will be built we don't really need to nail down a specific timezone but if you have pending changes, please try to get them in today.

If you have any questions or concerns about the release, please speak up.

I do have. It broke both mongo and mongo-morphia plugins for my applications:

http://grails.1312388.n4.nabble.com/Blocker-bug-for-Grails-2-0-1-no-Mongo-plugin-mongo-or-mongo-morphia-works-tt4384268.html

Just as an update, it also break my unit tests with the same error messages, even after removing any MongoDB plugins, although the application itself will work fine.

Opened a JIRA with a sample application demonstrating the issue:
http://jira.grails.org/browse/GRAILS-8769

Unfortunately I couldn't reproduce the exact behavior of my application. In my application the issue will raise in the first run of "grails test-app unit:".

In the sample application, some changes are required to be done in the source while on Grails interactive for raising the issue.

[smaldini]

I got a NPE in the same method (establishRelationship) when I made some tests with a real project , upgrading to  2.0.1.  and I debugged it a bit :

If you have an unidirectional hasMany domain and an untyped getter (ie: "def propertyName", "def myService") in your owned side, it fails with NPE in the same establishRelationShip than yours. This method is doomed !

As far as I know, at least on that one, Graeme is investigating, keep faith in 2.0.1 !

On Mon, Feb 13, 2012 at 8:04 PM, Rodrigo Rosenfeld Rosas <[hidden email]> wrote:

Em 13-02-2012 15:48, rosenfeld [via Grails] escreveu:

Em 13-02-2012 14:49, rosenfeld [via Grails] escreveu:

Em 10-02-2012 14:52, Jeff Brown-4 [via Grails] escreveu:

We would like to issue a code freeze on the 2.0.x branch around COB today  Because we have the weekend between today and when the release will be built we don't really need to nail down a specific timezone but if you have pending changes, please try to get them in today.

If you have any questions or concerns about the release, please speak up.

I do have. It broke both mongo and mongo-morphia plugins for my applications:

http://grails.1312388.n4.nabble.com/Blocker-bug-for-Grails-2-0-1-no-Mongo-plugin-mongo-or-mongo-morphia-works-tt4384268.html

Just as an update, it also break my unit tests with the same error messages, even after removing any MongoDB plugins, although the application itself will work fine.

Opened a JIRA with a sample application demonstrating the issue:
http://jira.grails.org/browse/GRAILS-8769

Unfortunately I couldn't reproduce the exact behavior of my application. In my application the issue will raise in the first run of "grails test-app unit:".

In the sample application, some changes are required to be done in the source while on Grails interactive for raising the issue.

--

Stéphane MALDINI

--