Grails 1.3.3 Release

[Jeff Brown-4]

Dear Groovy/Grails Community,

We are pleased to announce the release of Grails 1.3.3.  Please see the following links for more information:

Release Notes - http://grails.org/1.3.3+Release+Notes
Download - http://grails.org/Download

As always, thanks to everyone who contributed to the release.

Enjoy!



Jeff
--
Jeff Brown
[hidden email]<mailto:[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

[Marcus Better]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It seems to break half of my unit tests:

java.lang.NullPointerException
at grails.test.MockUtils.mockDomain(MockUtils.groovy:443)
at grails.test.MockUtils$mockDomain.call(Unknown Source)
at grails.test.GrailsUnitTestCase.mockDomain(GrailsUnitTestCase.groovy:131)
at grails.test.GrailsUnitTestCase.mockDomain(GrailsUnitTestCase.groovy:129)

Cheers,

Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkw137cACgkQXjXn6TzcAQny6QCfQU8Bee7LmKUUJBXG1ctCDfQD
MbIAoPA8uhdnrbKGDgECZ16pMI+Fk0lH
=Sd6+
-----END PGP SIGNATURE-----



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

    http://xircles.codehaus.org/manage_email

[Jeff Brown-3]

On Thu, Jul 8, 2010 at 9:24 AM, Marcus Better <[hidden email]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> It seems to break half of my unit tests:
>
> java.lang.NullPointerException
> at grails.test.MockUtils.mockDomain(MockUtils.groovy:443)
> at grails.test.MockUtils$mockDomain.call(Unknown Source)
> at grails.test.GrailsUnitTestCase.mockDomain(GrailsUnitTestCase.groovy:131)
> at grails.test.GrailsUnitTestCase.mockDomain(GrailsUnitTestCase.groovy:129)
>
> Cheers,
>

Is it breaking all of your tests that use mockDomain or some subset of
them?  I knew you said that it breaks "half of my unit tests", but I
am not sure if that is because half of your unit tests use mockDomain
or there is some other factor.



jb

--
Jeff Brown
SpringSource
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

[Jeff Brown-3]

On Thu, Jul 8, 2010 at 9:24 AM, Marcus Better <[hidden email]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> It seems to break half of my unit tests:
>
> java.lang.NullPointerException
> at grails.test.MockUtils.mockDomain(MockUtils.groovy:443)
> at grails.test.MockUtils$mockDomain.call(Unknown Source)
> at grails.test.GrailsUnitTestCase.mockDomain(GrailsUnitTestCase.groovy:131)
> at grails.test.GrailsUnitTestCase.mockDomain(GrailsUnitTestCase.groovy:129)
>
> Cheers,
>
> Marcus

I am trying to reproduce the problem and cannot so far.  If you can
share any specifics that would help reproduce the problem, that would
be useful.

Thanks.



jb
--
Jeff Brown
SpringSource
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

[Göran Ehrsson]

Thanks!

Just curious, why 1.3.3 was released so close after 1.3.2?
Any specific issue?

/Goran

Jeff Brown wrote 2010-07-08 15:31:

> Dear Groovy/Grails Community,
>
> We are pleased to announce the release of Grails 1.3.3.  Please see the following links for more information:
>
> Release Notes - http://grails.org/1.3.3+Release+Notes
> Download - http://grails.org/Download
>
> As always, thanks to everyone who contributed to the release.
>
> Enjoy!
>
>
>
> Jeff
> --
> Jeff Brown
> [hidden email]<mailto:[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

[Jeff Brown-3]

On Thu, Jul 8, 2010 at 10:31 AM, Goran Ehrsson <[hidden email]> wrote:
> Thanks!
>
> Just curious, why 1.3.3 was released so close after 1.3.2?
> Any specific issue?
>
> /Goran

The log of relevant JIRA issues is at
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11063&version=16545.
 This particular release is mostly bug fixes.

In general we have been producing smaller more frequent point
releases.  The time between this release and the previous has been
shorter than we will usually see but more frequent releases is where
we have been heading.

Having smaller more frequent releases benefits users in a number of
ways.  One benefit is that it gets fixes to users more quickly.  An
issue that one project might consider trivial may be a production show
stopper for some other project.  Getting these fixes out sooner
benefits the folks waiting for them.

The smaller more frequent releases also help folks manage their
application upgrades.  For teams who recently rolled out a 1.3.2
application, they can review the changelog for 1.3.3 and if there
isn't anything there to benefit their project, they can stay put and
skip a release (or more than 1 release).

I hope some of that information is helpful.



jb

--
Jeff Brown
SpringSource
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

[skadiy000]

Hi Jeff

Looks like a good move of minor point releases.

However, I have noticed that there is a lag to the availability of releases in maven repositories. For example at........

http://snapshots.repository.codehaus.org/org/grails/grails-core/


Is there any reason for this?


Which maven repository is immediately pumped up with the releases?

Thanks

[Ben Schreur]

Hi Jeff,

Just a few minutes ago I tried upgrading to 1.3.3 and I got similar error messages.

How to reproduce:

(0) Make sure grails is set to 1.3.3
(1) Check out this project from svn:
     svn checkout http://agiletrackingtool.googlecode.com/svn/trunk/ agiletrackingtool-read-onlysvn checkout
(2) go the the root of the grails project: grails upgrade (will upgrade from 1.3.2 to 1.3.3)
(3) Run grails test-app -unit

At the bottom of the mail I pasted the output of the unit tests.

When time permits I will do some investigation over the coming days.
This is my pet-project for evening fun. :-)

If you need help or have questions just mail.

Kind regards,
Ben

All Errors

Class	Name	Status	Type	Time(s)
ItemServiceTests	testRetrievingItemsThatBelongToProjectReturnsNoneWhenAllAreFinished	Error	N/A java.lang.NullPointerException at grails.test.MockUtils$_addValidateMethod_closure83.doCall(MockUtils.groovy:973) at grails.test.MockUtils$_addValidateMethod_closure84.doCall(MockUtils.groovy:1014) at grails.test.MockUtils$_addDynamicInstanceMethods_closure67.doCall(MockUtils.groovy:736) at grails.test.MockUtils$_addDynamicInstanceMethods_closure67.doCall(MockUtils.groovy) at org.agiletracking.ItemServiceTests.testRetrievingItemsThatBelongToProjectReturnsNoneWhenAllAreFinished(ItemServiceTests.groovy:80) at TestApp$_run_closure4.doCall(TestApp:268) at TestApp$_run_closure4.call(TestApp) at TestApp$_run_closure2.doCall(TestApp:225) at TestApp$_run_closure1_closure21.doCall(TestApp:184) at TestApp$_run_closure1.doCall(TestApp:171) at TestApp$_run_closure1.doCall(TestApp.groovy:101) at gant.Gant$_dispatch_closure5.doCall(Gant.groovy:381) at gant.Gant$_dispatch_closure7.doCall(Gant.groovy:415) at gant.Gant$_dispatch_closure7.doCall(Gant.groovy) at gant.Gant.withBuildListeners(Gant.groovy:427) at gant.Gant.this$2$withBuildListeners(Gant.groovy) at gant.Gant$this$2$withBuildListeners.callCurrent(Unknown Source) at gant.Gant.dispatch(Gant.groovy:415) at gant.Gant.this$2$dispatch(Gant.groovy) at gant.Gant.invokeMethod(Gant.groovy) at gant.Gant.executeTargets(Gant.groovy:590) at gant.Gant.executeTargets(Gant.groovy:589)	0.044
IterationServiceTests	testTransferItems	Error	N/A java.lang.NullPointerException at grails.test.MockUtils$_addValidateMethod_closure83.doCall(MockUtils.groovy:973) at grails.test.MockUtils$_addValidateMethod_closure84.doCall(MockUtils.groovy:1014) at grails.test.MockUtils$_addDynamicInstanceMethods_closure67.doCall(MockUtils.groovy:736) at grails.test.MockUtils$_addDynamicInstanceMethods_closure67.doCall(MockUtils.groovy) at org.agiletracking.IterationService.transferUnfinishedItems(IterationService.groovy:44) at org.agiletracking.IterationService$transferUnfinishedItems.call(Unknown Source) at org.agiletracking.IterationServiceTests.testTransferItems(IterationServiceTests.groovy:63) at TestApp$_run_closure4.doCall(TestApp:268) at TestApp$_run_closure4.call(TestApp) at TestApp$_run_closure2.doCall(TestApp:225) at TestApp$_run_closure1_closure21.doCall(TestApp:184) at TestApp$_run_closure1.doCall(TestApp:171) at TestApp$_run_closure1.doCall(TestApp.groovy:101) at gant.Gant$_dispatch_closure5.doCall(Gant.groovy:381) at gant.Gant$_dispatch_closure7.doCall(Gant.groovy:415) at gant.Gant$_dispatch_closure7.doCall(Gant.groovy) at gant.Gant.withBuildListeners(Gant.groovy:427) at gant.Gant.this$2$withBuildListeners(Gant.groovy) at gant.Gant$this$2$withBuildListeners.callCurrent(Unknown Source) at gant.Gant.dispatch(Gant.groovy:415) at gant.Gant.this$2$dispatch(Gant.groovy) at gant.Gant.invokeMethod(Gant.groovy) at gant.Gant.executeTargets(Gant.groovy:590) at gant.Gant.executeTargets(Gant.groovy:589)	0.071
ProjectServiceTests	testAddGroupToNewProject	Error	N/A java.lang.NullPointerException at grails.test.MockUtils$_addValidateMethod_closure83.doCall(MockUtils.groovy:973) at grails.test.MockUtils$_addValidateMethod_closure84.doCall(MockUtils.groovy:1014) at grails.test.MockUtils$_addDynamicInstanceMethods_closure67.doCall(MockUtils.groovy:736) at grails.test.MockUtils$_addDynamicInstanceMethods_closure67.doCall(MockUtils.groovy) at org.agiletracking.ProjectService.addGroupToNewProject(ProjectService.groovy:33) at org.agiletracking.ProjectService$addGroupToNewProject.call(Unknown Source) at org.agiletracking.ProjectServiceTests.testAddGroupToNewProject(ProjectServiceTests.groovy:114) at TestApp$_run_closure4.doCall(TestApp:268) at TestApp$_run_closure4.call(TestApp) at TestApp$_run_closure2.doCall(TestApp:225) at TestApp$_run_closure1_closure21.doCall(TestApp:184) at TestApp$_run_closure1.doCall(TestApp:171) at TestApp$_run_closure1.doCall(TestApp.groovy:101) at gant.Gant$_dispatch_closure5.doCall(Gant.groovy:381) at gant.Gant$_dispatch_closure7.doCall(Gant.groovy:415) at gant.Gant$_dispatch_closure7.doCall(Gant.groovy) at gant.Gant.withBuildListeners(Gant.groovy:427) at gant.Gant.this$2$withBuildListeners(Gant.groovy) at gant.Gant$this$2$withBuildListeners.callCurrent(Unknown Source) at gant.Gant.dispatch(Gant.groovy:415) at gant.Gant.this$2$dispatch(Gant.groovy) at gant.Gant.invokeMethod(Gant.groovy) at gant.Gant.executeTargets(Gant.groovy:590) at gant.Gant.executeTargets(Gant.groovy:589)	0.253
ProjectTests	testSave	Error	N/A java.lang.NullPointerException at grails.test.MockUtils$_addValidateMethod_closure83.doCall(MockUtils.groovy:973) at grails.test.MockUtils$_addValidateMethod_closure84.doCall(MockUtils.groovy:1014) at org.agiletracking.ProjectTests.testSave(ProjectTests.groovy:41) at TestApp$_run_closure4.doCall(TestApp:268) at TestApp$_run_closure4.call(TestApp) at TestApp$_run_closure2.doCall(TestApp:225) at TestApp$_run_closure1_closure21.doCall(TestApp:184) at TestApp$_run_closure1.doCall(TestApp:171) at TestApp$_run_closure1.doCall(TestApp.groovy:101) at gant.Gant$_dispatch_closure5.doCall(Gant.groovy:381) at gant.Gant$_dispatch_closure7.doCall(Gant.groovy:415) at gant.Gant$_dispatch_closure7.doCall(Gant.groovy) at gant.Gant.withBuildListeners(Gant.groovy:427) at gant.Gant.this$2$withBuildListeners(Gant.groovy) at gant.Gant$this$2$withBuildListeners.callCurrent(Unknown Source) at gant.Gant.dispatch(Gant.groovy:415) at gant.Gant.this$2$dispatch(Gant.groovy) at gant.Gant.invokeMethod(Gant.groovy) at gant.Gant.executeTargets(Gant.groovy:590) at gant.Gant.executeTargets(Gant.groovy:589)

2010/7/8 Jeff Brown <[hidden email]>

On Thu, Jul 8, 2010 at 9:24 AM, Marcus Better <[hidden email]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> It seems to break half of my unit tests:
>
> java.lang.NullPointerException
> at grails.test.MockUtils.mockDomain(MockUtils.groovy:443)
> at grails.test.MockUtils$mockDomain.call(Unknown Source)
> at grails.test.GrailsUnitTestCase.mockDomain(GrailsUnitTestCase.groovy:131)
> at grails.test.GrailsUnitTestCase.mockDomain(GrailsUnitTestCase.groovy:129)
>
> Cheers,
>
> Marcus

I am trying to reproduce the problem and cannot so far.  If you can
share any specifics that would help reproduce the problem, that would
be useful.

Thanks.



jb
--
Jeff Brown
SpringSource

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

[John Fletcher-3]

2010/7/8 Jeff Brown

In general we have been producing smaller more frequent point
releases.

I like it. It also makes the project seem more alive/active, somehow.

- John

[Jeff Brown-3]

On Thu, Jul 8, 2010 at 2:27 PM, Ben Schreur <[hidden email]> wrote:

Hi Jeff,

Just a few minutes ago I tried upgrading to 1.3.3 and I got similar error messages.

How to reproduce:

(0) Make sure grails is set to 1.3.3
(1) Check out this project from svn:
     svn checkout http://agiletrackingtool.googlecode.com/svn/trunk/ agiletrackingtool-read-onlysvn checkout
(2) go the the root of the grails project: grails upgrade (will upgrade from 1.3.2 to 1.3.3)
(3) Run grails test-app -unit

That will be helpful.  I am about to board a plane but will investigate this as soon as I can.

In the meantime, if one of you would create a relevant JIRA to track the issue, we will get it resolved right away.

Thanks for the info.

jb

--
Jeff Brown
SpringSource
http://www.springsource.com/

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

[Göran Ehrsson]

Thanks Jeff, this is good news. I like smaller more frequent point releases.
I have been running six production sites on Grails 1.3.2 for 2-3 weeks
now without any problem. And I got worried that I missed something when
I read the 1.3.3 change log without finding any severe issues affecting
me. But now I understand I dont have to worry.

Keep up the good work!

Regards.

/Goran Ehrsson


Jeff Brown wrote 2010-07-08 18:11:

> On Thu, Jul 8, 2010 at 10:31 AM, Goran Ehrsson<[hidden email]>  wrote:
>    
>> Thanks!
>>
>> Just curious, why 1.3.3 was released so close after 1.3.2?
>> Any specific issue?
>>
>> /Goran
>>      
> The log of relevant JIRA issues is at
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11063&version=16545.
>   This particular release is mostly bug fixes.
>
> In general we have been producing smaller more frequent point
> releases.  The time between this release and the previous has been
> shorter than we will usually see but more frequent releases is where
> we have been heading.
>
> Having smaller more frequent releases benefits users in a number of
> ways.  One benefit is that it gets fixes to users more quickly.  An
> issue that one project might consider trivial may be a production show
> stopper for some other project.  Getting these fixes out sooner
> benefits the folks waiting for them.
>
> The smaller more frequent releases also help folks manage their
> application upgrades.  For teams who recently rolled out a 1.3.2
> application, they can review the changelog for 1.3.3 and if there
> isn't anything there to benefit their project, they can stay put and
> skip a release (or more than 1 release).
>
> I hope some of that information is helpful.
>
>
>
> jb
>
>    

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

    http://xircles.codehaus.org/manage_email

[rvanderwerf]

Anyone else having issues installing jetty on this version?
I have upgraded from 1.3.1, and keep getting this error trying to install jetty. Or is it no longer available going forward?

Resolving dependencies...
Dependencies resolved in 884ms.
Running script /opt/grails-1.3.3/scripts/InstallPlugin.groovy
Environment set to development
Resolving plugin jetty. Please wait...

Downloading: http://plugins.grails.org//grails-jetty/tags/RELEASE_1_2-SNAPSHOT/grails-jetty-1.2-SNAPSHOT.zip ...
Download complete.
Installing zip /home/rvanderwerf/.ivy2/cache/org.grails.plugins/jetty/zips/jetty-1.2-SNAPSHOT.zip... ...
    [mkdir] Created dir: /home/rvanderwerf/.grails/1.3.3/projects/grails1-3-1-mdpcore-v2/plugins/jetty-1.2-SNAPSHOT
    [unzip] Expanding: /home/rvanderwerf/.ivy2/cache/org.grails.plugins/jetty/zips/jetty-1.2-SNAPSHOT.zip into /home/rvanderwerf/.grails/1.3.3/projects/grails1-3-1-mdpcore-v2/plugins/jetty-1.2-SNAPSHOT
Installed plugin jetty-1.2-SNAPSHOT to location /home/rvanderwerf/.grails/1.3.3/projects/grails1-3-1-mdpcore-v2/plugins/jetty-1.2-SNAPSHOT. ...
Resolving plugin JAR dependencies ...
:: problems summary ::
:::: WARNINGS
                [FAILED     ] org.mortbay.jetty#jsp-2.0;6.1.21!jsp-2.0.jar:  (0ms)
:::::::::::::::::::::::::::::::::::::::::::::

                ::              FAILED DOWNLOADS            ::

                :: ^ see resolution messages for details  ^ ::

                ::::::::::::::::::::::::::::::::::::::::::::::

                :: org.mortbay.jetty#jsp-2.0;6.1.21!jsp-2.0.jar

                ::::::::::::::::::::::::::::::::::::::::::::::


Failed to install plugin [jetty-1.2-SNAPSHOT]. Plugin has missing JAR dependencies.
jsp-2.0-6.1.21.jar
----- Original Message -----
From: "Jeff Brown" <[hidden email]>
To: "Grails User" <[hidden email]>, "Groovy Users" <[hidden email]>
Sent: Thursday, July 8, 2010 8:31:21 AM GMT -06:00 US/Canada Central
Subject: [grails-user] Grails 1.3.3 Release

Dear Groovy/Grails Community,

We are pleased to announce the release of Grails 1.3.3.  Please see the following links for more information:

Release Notes - http://grails.org/1.3.3+Release+Notes
Download - http://grails.org/Download

As always, thanks to everyone who contributed to the release.

Enjoy!



Jeff
--
Jeff Brown
[hidden email]<mailto:[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



--

NOTICE: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. Nothing contained in this message or in any attachment shall constitute a contract or electronic signature under the Electronic Signatures in Global and National Commerce Act, any version of the Uniform Electronic Transactions Act or any other statute governing electronic transactions.

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

    http://xircles.codehaus.org/manage_email

[René Gröschke]

Hi there,
I've updated the macports (http://www.macports.org) support for grails
to version 1.3.3.

regards,
René


Am 08.07.10 15:31, schrieb Jeff Brown:

> Dear Groovy/Grails Community,
>
> We are pleased to announce the release of Grails 1.3.3.  Please see the following links for more information:
>
> Release Notes - http://grails.org/1.3.3+Release+Notes
> Download - http://grails.org/Download
>
> As always, thanks to everyone who contributed to the release.
>
> Enjoy!
>
>
>
> Jeff
> --
> Jeff Brown
> [hidden email]<mailto:[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
>
>
>    

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

    http://xircles.codehaus.org/manage_email

[Björn Wilmsmann-2]

Thanks a bunch. I really appreciate the shorter release cycle :)

On 8 July 2010 15:31, Jeff Brown <[hidden email]> wrote:
> Dear Groovy/Grails Community,
>
> We are pleased to announce the release of Grails 1.3.3.  Please see the following links for more information:
>
> Release Notes - http://grails.org/1.3.3+Release+Notes
> Download - http://grails.org/Download
>
> As always, thanks to everyone who contributed to the release.

--
Best regards,
Björn Wilmsmann

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

    http://xircles.codehaus.org/manage_email

[Marcus Better]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeff Brown wrote:
> In the meantime, if one of you would create a relevant JIRA to track the
> issue, we will get it resolved right away.

Filed GRAILS-6482.

Cheers,

Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkw2OdYACgkQXjXn6TzcAQmovACeLtCyFJp5cxqo0Fb8RenqzgnB
CacAoOKP9I/Nj6Ytn5TQrjDB3GgQ9/wt
=bMFb
-----END PGP SIGNATURE-----



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

    http://xircles.codehaus.org/manage_email

[Robert La Ferla-6]

On 7/8/2010 12:11 PM, Jeff Brown wrote:
> Having smaller more frequent releases benefits users in a number of
> ways.  One benefit is that it gets fixes to users more quickly.  An
> issue that one project might consider trivial may be a production show
> stopper for some other project.  Getting these fixes out sooner
> benefits the folks waiting for them.
>    

Absolutely.  Smaller more frequent releases are better.  Thanks for all
your effort in improving Grails.

--
- --
Robert La Ferla
VP Engineering
OMS SafeHarbor

This message (and any attachments) contains confidential information and is protected by law.  If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, distribution, or the taking of any action based on this message, is strictly prohibited.


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

    http://xircles.codehaus.org/manage_email

[burtbeckwith]

Please see my comment at http://jira.codehaus.org/browse/GRAILS-6482 for a simple workaround you can add to your tests until this issue is fixed.

Burt

> Jeff Brown wrote:
> > In the meantime, if one of you would create a relevant JIRA to track the
> > issue, we will get it resolved right away.
>
> Filed GRAILS-6482.
>
> Cheers,
>
> Marcus

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

    http://xircles.codehaus.org/manage_email

[Robert Fletcher-2]

Yes, I'm seeing the same issue. This bug appeared in Grails 1.3.2. I
thought it had been fixed as part of
http://jira.codehaus.org/browse/GRAILS-6420 but apparently not. I'll
update http://jira.codehaus.org/browse/GRAILS-6427

On Thu, Jul 8, 2010 at 9:00 PM, Ryan Vanderwerf
<[hidden email]> wrote:

> Anyone else having issues installing jetty on this version?
> I have upgraded from 1.3.1, and keep getting this error trying to install jetty. Or is it no longer available going forward?
>
> Resolving dependencies...
> Dependencies resolved in 884ms.
> Running script /opt/grails-1.3.3/scripts/InstallPlugin.groovy
> Environment set to development
> Resolving plugin jetty. Please wait...
>
> Downloading: http://plugins.grails.org//grails-jetty/tags/RELEASE_1_2-SNAPSHOT/grails-jetty-1.2-SNAPSHOT.zip ...
> Download complete.
> Installing zip /home/rvanderwerf/.ivy2/cache/org.grails.plugins/jetty/zips/jetty-1.2-SNAPSHOT.zip... ...
>    [mkdir] Created dir: /home/rvanderwerf/.grails/1.3.3/projects/grails1-3-1-mdpcore-v2/plugins/jetty-1.2-SNAPSHOT
>    [unzip] Expanding: /home/rvanderwerf/.ivy2/cache/org.grails.plugins/jetty/zips/jetty-1.2-SNAPSHOT.zip into /home/rvanderwerf/.grails/1.3.3/projects/grails1-3-1-mdpcore-v2/plugins/jetty-1.2-SNAPSHOT
> Installed plugin jetty-1.2-SNAPSHOT to location /home/rvanderwerf/.grails/1.3.3/projects/grails1-3-1-mdpcore-v2/plugins/jetty-1.2-SNAPSHOT. ...
> Resolving plugin JAR dependencies ...
> :: problems summary ::
> :::: WARNINGS
>                [FAILED     ] org.mortbay.jetty#jsp-2.0;6.1.21!jsp-2.0.jar:  (0ms)
> :::::::::::::::::::::::::::::::::::::::::::::
>
>                ::              FAILED DOWNLOADS            ::
>
>                :: ^ see resolution messages for details  ^ ::
>
>                ::::::::::::::::::::::::::::::::::::::::::::::
>
>                :: org.mortbay.jetty#jsp-2.0;6.1.21!jsp-2.0.jar
>
>                ::::::::::::::::::::::::::::::::::::::::::::::
>
>
> Failed to install plugin [jetty-1.2-SNAPSHOT]. Plugin has missing JAR dependencies.
> jsp-2.0-6.1.21.jar
> ----- Original Message -----
> From: "Jeff Brown" <[hidden email]>
> To: "Grails User" <[hidden email]>, "Groovy Users" <[hidden email]>
> Sent: Thursday, July 8, 2010 8:31:21 AM GMT -06:00 US/Canada Central
> Subject: [grails-user] Grails 1.3.3 Release
>
> Dear Groovy/Grails Community,
>
> We are pleased to announce the release of Grails 1.3.3.  Please see the following links for more information:
>
> Release Notes - http://grails.org/1.3.3+Release+Notes
> Download - http://grails.org/Download
>
> As always, thanks to everyone who contributed to the release.
>
> Enjoy!
>
>
>
> Jeff
> --
> Jeff Brown
> [hidden email]<mailto:[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
>
>
>
> --
>
> NOTICE: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. Nothing contained in this message or in any attachment shall constitute a contract or electronic signature under the Electronic Signatures in Global and National Commerce Act, any version of the Uniform Electronic Transactions Act or any other statute governing electronic transactions.
>
> ---------------------------------------------------------------------
> 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

[Inam]

Hi,

I just upgrade grails from 1.2.2 to 1.3.3 and every thing went fine (no plugin problem which was in 1.3.2) except one exception which occurs while autobase migration script executes, the stake trace is:

---

Caused by: java.lang.RuntimeException: Unknown tag: preConditions
        at liquibase.change.ChangeFactory.create(ChangeFactory.java:88)
        at liquibase.parser.factory.OpenChangeFactory.create(OpenChangeFactory.groovy:52)
        at liquibase.parser.factory.OpenChangeFactory$create.call(Unknown Source)
        at liquibase.dsl.parser.groovy.GroovyChangeSet.methodMissing(GroovyChangeSet.groovy:82)
        at liquibase.dsl.parser.groovy.GroovyChangeSet.invokeMethod(GroovyChangeSet.groovy)
        at Script1$_run_closure1_closure2.doCall(Script1.groovy:3)
        at Script1$_run_closure1_closure2.doCall(Script1.groovy)
        at liquibase.dsl.parser.groovy.GroovyDatabaseChangeLog.changeSet(GroovyDatabaseChangeLog.groovy:57)
        at liquibase.dsl.parser.groovy.GroovyDatabaseChangeLog.changeSet(GroovyDatabaseChangeLog.groovy)
        at Script1$_run_closure1.doCall(Script1.groovy:2)
        at liquibase.dsl.parser.groovy.GroovyDatabaseChangeLog.include(GroovyDatabaseChangeLog.groovy:146)
        ... 43 more
---

please help, whats went wrong there?

Thanks,
Inam.

[Dean Del Ponte-2]

Thanks!  Great stuff!  We're doing all new development in Grails here and slowly transitioning legacy systems over to it when it makes sense.

It's the best framework I've used so far.

Keep it up!

Dean Del Ponte

On Thu, Jul 8, 2010 at 11:43 PM, Robert Fletcher <[hidden email]> wrote:

Yes, I'm seeing the same issue. This bug appeared in Grails 1.3.2. I
thought it had been fixed as part of
http://jira.codehaus.org/browse/GRAILS-6420 but apparently not. I'll
update http://jira.codehaus.org/browse/GRAILS-6427

On Thu, Jul 8, 2010 at 9:00 PM, Ryan Vanderwerf
<[hidden email]> wrote:
> Anyone else having issues installing jetty on this version?
> I have upgraded from 1.3.1, and keep getting this error trying to install jetty. Or is it no longer available going forward?
>
> Resolving dependencies...
> Dependencies resolved in 884ms.
> Running script /opt/grails-1.3.3/scripts/InstallPlugin.groovy
> Environment set to development
> Resolving plugin jetty. Please wait...
>
> Downloading: http://plugins.grails.org//grails-jetty/tags/RELEASE_1_2-SNAPSHOT/grails-jetty-1.2-SNAPSHOT.zip ...
> Download complete.
> Installing zip /home/rvanderwerf/.ivy2/cache/org.grails.plugins/jetty/zips/jetty-1.2-SNAPSHOT.zip... ...
>    [mkdir] Created dir: /home/rvanderwerf/.grails/1.3.3/projects/grails1-3-1-mdpcore-v2/plugins/jetty-1.2-SNAPSHOT
>    [unzip] Expanding: /home/rvanderwerf/.ivy2/cache/org.grails.plugins/jetty/zips/jetty-1.2-SNAPSHOT.zip into /home/rvanderwerf/.grails/1.3.3/projects/grails1-3-1-mdpcore-v2/plugins/jetty-1.2-SNAPSHOT
> Installed plugin jetty-1.2-SNAPSHOT to location /home/rvanderwerf/.grails/1.3.3/projects/grails1-3-1-mdpcore-v2/plugins/jetty-1.2-SNAPSHOT. ...
> Resolving plugin JAR dependencies ...
> :: problems summary ::
> :::: WARNINGS
>                [FAILED     ] org.mortbay.jetty#jsp-2.0;6.1.21!jsp-2.0.jar:  (0ms)
> :::::::::::::::::::::::::::::::::::::::::::::
>
>                ::              FAILED DOWNLOADS            ::
>
>                :: ^ see resolution messages for details  ^ ::
>
>                ::::::::::::::::::::::::::::::::::::::::::::::
>
>                :: org.mortbay.jetty#jsp-2.0;6.1.21!jsp-2.0.jar
>
>                ::::::::::::::::::::::::::::::::::::::::::::::
>
>
> Failed to install plugin [jetty-1.2-SNAPSHOT]. Plugin has missing JAR dependencies.
> jsp-2.0-6.1.21.jar
> ----- Original Message -----
> From: "Jeff Brown" <[hidden email]>
> To: "Grails User" <[hidden email]>, "Groovy Users" <[hidden email]>
> Sent: Thursday, July 8, 2010 8:31:21 AM GMT -06:00 US/Canada Central
> Subject: [grails-user] Grails 1.3.3 Release
>
> Dear Groovy/Grails Community,
>
> We are pleased to announce the release of Grails 1.3.3.  Please see the following links for more information:
>
> Release Notes - http://grails.org/1.3.3+Release+Notes
> Download - http://grails.org/Download
>
> As always, thanks to everyone who contributed to the release.
>
> Enjoy!
>
>
>
> Jeff
> --
> Jeff Brown
> [hidden email]<mailto:[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
>
>
>
> --
>
> NOTICE: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. Nothing contained in this message or in any attachment shall constitute a contract or electronic signature under the Electronic Signatures in Global and National Commerce Act, any version of the Uniform Electronic Transactions Act or any other statute governing electronic transactions.
>
> ---------------------------------------------------------------------
> 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