ANN: Grails 3 Milestone 1 Released

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

ANN: Grails 3 Milestone 1 Released

Graeme Rocher-2
Hi all,

We have released Grails 3 Milestone 1 and it can be downloaded from
the new location at:

https://github.com/grails/grails-core/releases/tag/v3.0.0.M1

If you are a plugin author now is the time to consider looking at
porting your plugins to Grails 3.

You can find some example plugins here:

https://github.com/grails3-plugins/

In particular with the code gen and build system based on Gradle some
plugins that interact heavily with the command line will require
updates.

I have posted a video of Grails 3 in action on YouTube:

https://www.youtube.com/watch?v=aro3_RZqgtU

Hopefully this will get you excited to consider updating plugins. For
publishing we recommend publishing your plugin to Bintray. We will be
working on a Bintray based Grails 3 plugin portal soon. The previous
portal will continue for Grails 2 plugins.

We look forward to the plugin community help drive forward Grails 3

Thanks, and look forward to your feedback.

--
Graeme Rocher

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

Alvaro Sanchez-Mariscal
This is excellent news! 

Is there any organized way we can help upgrading plugins? I'm thinking on the current "core" plugins (the ones flagged as supported by Pivotal), like Spring Security Core.

Cheers.

2015-01-29 11:59 GMT+01:00 Graeme Rocher <[hidden email]>:
Hi all,

We have released Grails 3 Milestone 1 and it can be downloaded from
the new location at:

https://github.com/grails/grails-core/releases/tag/v3.0.0.M1

If you are a plugin author now is the time to consider looking at
porting your plugins to Grails 3.

You can find some example plugins here:

https://github.com/grails3-plugins/

In particular with the code gen and build system based on Gradle some
plugins that interact heavily with the command line will require
updates.

I have posted a video of Grails 3 in action on YouTube:

https://www.youtube.com/watch?v=aro3_RZqgtU

Hopefully this will get you excited to consider updating plugins. For
publishing we recommend publishing your plugin to Bintray. We will be
working on a Bintray based Grails 3 plugin portal soon. The previous
portal will continue for Grails 2 plugins.

We look forward to the plugin community help drive forward Grails 3

Thanks, and look forward to your feedback.

--
Graeme Rocher

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.



--

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CANWPwkTsqRG3puVcMbPcO-nKBQ4H4_hWV0TQU_5RdVB2w9ukdg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

Graeme Rocher-2
I plan to look at Spring Security Core soon, but a great area to
contribute would be forking and trying to port some of the popular
community developed plugins:

https://grails.org/plugins/?filter=installed

Like 'mail' etc. since they are just JAR files they can be published
to Bintray for the moment

Thanks

On Thu, Jan 29, 2015 at 12:21 PM, Alvaro Sanchez-Mariscal
<[hidden email]> wrote:

> This is excellent news!
>
> Is there any organized way we can help upgrading plugins? I'm thinking on
> the current "core" plugins (the ones flagged as supported by Pivotal), like
> Spring Security Core.
>
> Cheers.
>
> 2015-01-29 11:59 GMT+01:00 Graeme Rocher <[hidden email]>:
>>
>> Hi all,
>>
>> We have released Grails 3 Milestone 1 and it can be downloaded from
>> the new location at:
>>
>> https://github.com/grails/grails-core/releases/tag/v3.0.0.M1
>>
>> If you are a plugin author now is the time to consider looking at
>> porting your plugins to Grails 3.
>>
>> You can find some example plugins here:
>>
>> https://github.com/grails3-plugins/
>>
>> In particular with the code gen and build system based on Gradle some
>> plugins that interact heavily with the command line will require
>> updates.
>>
>> I have posted a video of Grails 3 in action on YouTube:
>>
>> https://www.youtube.com/watch?v=aro3_RZqgtU
>>
>> Hopefully this will get you excited to consider updating plugins. For
>> publishing we recommend publishing your plugin to Bintray. We will be
>> working on a Bintray based Grails 3 plugin portal soon. The previous
>> portal will continue for Grails 2 plugins.
>>
>> We look forward to the plugin community help drive forward Grails 3
>>
>> Thanks, and look forward to your feedback.
>>
>> --
>> Graeme Rocher
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Grails Dev Discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [hidden email].
>> To post to this group, send email to [hidden email].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Alvaro Sanchez-Mariscal
> [hidden email]
> twitter.com/alvaro_sanchez
>
> --
> You received this message because you are subscribed to the Google Groups
> "Grails Dev Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [hidden email].
> To post to this group, send email to [hidden email].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grails-dev-discuss/CANWPwkTsqRG3puVcMbPcO-nKBQ4H4_hWV0TQU_5RdVB2w9ukdg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



--
Graeme Rocher

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNoc9kuCEmmRNu8Jc0pKyLO%2BT0zVVSFTPUyOKd4Ax_ZCmVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

longwa
Any idea when the Upgrade Guide from 2.x will be finished?

I don't really want to beat my head against things that might end up in there as required changes.

Thanks,
Aaron

On Thursday, January 29, 2015 at 6:26:58 AM UTC-5, Graeme Rocher wrote:
I plan to look at Spring Security Core soon, but a great area to
contribute would be forking and trying to port some of the popular
community developed plugins:

<a href="https://grails.org/plugins/?filter=installed" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgrails.org%2Fplugins%2F%3Ffilter%3Dinstalled\46sa\75D\46sntz\0751\46usg\75AFQjCNGtQbr8HbFchLxgrpdIGJZAAVKusw';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgrails.org%2Fplugins%2F%3Ffilter%3Dinstalled\46sa\75D\46sntz\0751\46usg\75AFQjCNGtQbr8HbFchLxgrpdIGJZAAVKusw';return true;">https://grails.org/plugins/?filter=installed

Like 'mail' etc. since they are just JAR files they can be published
to Bintray for the moment

Thanks

On Thu, Jan 29, 2015 at 12:21 PM, Alvaro Sanchez-Mariscal
<<a href="javascript:" target="_blank" gdf-obfuscated-mailto="2mHBC6vPNHoJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">alvaro.sanc...@gmail.com> wrote:

> This is excellent news!
>
> Is there any organized way we can help upgrading plugins? I'm thinking on
> the current "core" plugins (the ones flagged as supported by Pivotal), like
> Spring Security Core.
>
> Cheers.
>
> 2015-01-29 11:59 GMT+01:00 Graeme Rocher <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="2mHBC6vPNHoJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">graeme...@...>:
>>
>> Hi all,
>>
>> We have released Grails 3 Milestone 1 and it can be downloaded from
>> the new location at:
>>
>> <a href="https://github.com/grails/grails-core/releases/tag/v3.0.0.M1" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Freleases%2Ftag%2Fv3.0.0.M1\46sa\75D\46sntz\0751\46usg\75AFQjCNE8DuRc-U9sniBXV4R5liIL37cqJA';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Freleases%2Ftag%2Fv3.0.0.M1\46sa\75D\46sntz\0751\46usg\75AFQjCNE8DuRc-U9sniBXV4R5liIL37cqJA';return true;">https://github.com/grails/grails-core/releases/tag/v3.0.0.M1
>>
>> If you are a plugin author now is the time to consider looking at
>> porting your plugins to Grails 3.
>>
>> You can find some example plugins here:
>>
>> <a href="https://github.com/grails3-plugins/" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails3-plugins%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNHNOojpI3eMW8odZ4K-YNTFpNdX9g';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails3-plugins%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNHNOojpI3eMW8odZ4K-YNTFpNdX9g';return true;">https://github.com/grails3-plugins/
>>
>> In particular with the code gen and build system based on Gradle some
>> plugins that interact heavily with the command line will require
>> updates.
>>
>> I have posted a video of Grails 3 in action on YouTube:
>>
>> <a href="https://www.youtube.com/watch?v=aro3_RZqgtU" target="_blank" rel="nofollow" onmousedown="this.href='https://www.youtube.com/watch?v\75aro3_RZqgtU';return true;" onclick="this.href='https://www.youtube.com/watch?v\75aro3_RZqgtU';return true;">https://www.youtube.com/watch?v=aro3_RZqgtU
>>
>> Hopefully this will get you excited to consider updating plugins. For
>> publishing we recommend publishing your plugin to Bintray. We will be
>> working on a Bintray based Grails 3 plugin portal soon. The previous
>> portal will continue for Grails 2 plugins.
>>
>> We look forward to the plugin community help drive forward Grails 3
>>
>> Thanks, and look forward to your feedback.
>>
>> --
>> Graeme Rocher
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Grails Dev Discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="2mHBC6vPNHoJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">grails-dev-discuss+unsubscribe@....
>> To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="2mHBC6vPNHoJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">grails-de...@googlegroups.com.
>> To view this discussion on the web visit
>> <a href="https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com" target="_blank" rel="nofollow" onmousedown="this.href='https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com';return true;" onclick="this.href='https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com';return true;">https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com.
>> For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href='https://groups.google.com/d/optout';return true;" onclick="this.href='https://groups.google.com/d/optout';return true;">https://groups.google.com/d/optout.
>
>
>
>
> --
> Alvaro Sanchez-Mariscal
> <a href="javascript:" target="_blank" gdf-obfuscated-mailto="2mHBC6vPNHoJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">alvaro.sanc...@gmail.com
> <a href="http://twitter.com/alvaro_sanchez" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Ftwitter.com%2Falvaro_sanchez\46sa\75D\46sntz\0751\46usg\75AFQjCNGCC00ScTWh23pzOU3JLYTKkc7Acg';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Ftwitter.com%2Falvaro_sanchez\46sa\75D\46sntz\0751\46usg\75AFQjCNGCC00ScTWh23pzOU3JLYTKkc7Acg';return true;">twitter.com/alvaro_sanchez
>
> --
> You received this message because you are subscribed to the Google Groups
> "Grails Dev Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="2mHBC6vPNHoJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">grails-dev-discuss+unsubscribe@....
> To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="2mHBC6vPNHoJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">grails-de...@googlegroups.com.
> To view this discussion on the web visit
> <a href="https://groups.google.com/d/msgid/grails-dev-discuss/CANWPwkTsqRG3puVcMbPcO-nKBQ4H4_hWV0TQU_5RdVB2w9ukdg%40mail.gmail.com" target="_blank" rel="nofollow" onmousedown="this.href='https://groups.google.com/d/msgid/grails-dev-discuss/CANWPwkTsqRG3puVcMbPcO-nKBQ4H4_hWV0TQU_5RdVB2w9ukdg%40mail.gmail.com';return true;" onclick="this.href='https://groups.google.com/d/msgid/grails-dev-discuss/CANWPwkTsqRG3puVcMbPcO-nKBQ4H4_hWV0TQU_5RdVB2w9ukdg%40mail.gmail.com';return true;">https://groups.google.com/d/msgid/grails-dev-discuss/CANWPwkTsqRG3puVcMbPcO-nKBQ4H4_hWV0TQU_5RdVB2w9ukdg%40mail.gmail.com.
> For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href='https://groups.google.com/d/optout';return true;" onclick="this.href='https://groups.google.com/d/optout';return true;">https://groups.google.com/d/optout.



--
Graeme Rocher

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/e0ea01f3-0a42-47b6-bc3c-f82aa4a2df46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

Henrique Lobo Weissmann
In reply to this post by Graeme Rocher-2
Will there be any compatibility mode with previous Gant scripts?

It whould help a lot of people which have customized build processes.

On Thu, Jan 29, 2015 at 8:59 AM, Graeme Rocher <[hidden email]> wrote:
Hi all,

We have released Grails 3 Milestone 1 and it can be downloaded from
the new location at:

https://github.com/grails/grails-core/releases/tag/v3.0.0.M1

If you are a plugin author now is the time to consider looking at
porting your plugins to Grails 3.

You can find some example plugins here:

https://github.com/grails3-plugins/

In particular with the code gen and build system based on Gradle some
plugins that interact heavily with the command line will require
updates.

I have posted a video of Grails 3 in action on YouTube:

https://www.youtube.com/watch?v=aro3_RZqgtU

Hopefully this will get you excited to consider updating plugins. For
publishing we recommend publishing your plugin to Bintray. We will be
working on a Bintray based Grails 3 plugin portal soon. The previous
portal will continue for Grails 2 plugins.

We look forward to the plugin community help drive forward Grails 3

Thanks, and look forward to your feedback.

--
Graeme Rocher

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.



--
Henrique Lobo Weissmann (Kico)
(55) 31 9226-0459
http://devkico.itexto.com.br
http://www.twitter.com/loboweissmann

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAKQDOQW0adCD8HGUX5jYn9hQ2kCzAyWFkcnquq1RW6VL-YE%2BJg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

cfaddict
Awesome work guys! Looking forward to kicking the tires around. It appears that the build / run / test speeds are all going to be vastly improved which I am looking forward to.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/98b90fb7-1b2d-4947-baaf-4506d59be533%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

Graeme Rocher-2
In reply to this post by Henrique Lobo Weissmann
Unfortunately no, but the new API is way more elegant. I hope folks
pick it up and run with it :)

On Thu, Jan 29, 2015 at 8:19 PM, Henrique Lobo Weissmann
<[hidden email]> wrote:

> Will there be any compatibility mode with previous Gant scripts?
>
> It whould help a lot of people which have customized build processes.
>
> On Thu, Jan 29, 2015 at 8:59 AM, Graeme Rocher <[hidden email]>
> wrote:
>>
>> Hi all,
>>
>> We have released Grails 3 Milestone 1 and it can be downloaded from
>> the new location at:
>>
>> https://github.com/grails/grails-core/releases/tag/v3.0.0.M1
>>
>> If you are a plugin author now is the time to consider looking at
>> porting your plugins to Grails 3.
>>
>> You can find some example plugins here:
>>
>> https://github.com/grails3-plugins/
>>
>> In particular with the code gen and build system based on Gradle some
>> plugins that interact heavily with the command line will require
>> updates.
>>
>> I have posted a video of Grails 3 in action on YouTube:
>>
>> https://www.youtube.com/watch?v=aro3_RZqgtU
>>
>> Hopefully this will get you excited to consider updating plugins. For
>> publishing we recommend publishing your plugin to Bintray. We will be
>> working on a Bintray based Grails 3 plugin portal soon. The previous
>> portal will continue for Grails 2 plugins.
>>
>> We look forward to the plugin community help drive forward Grails 3
>>
>> Thanks, and look forward to your feedback.
>>
>> --
>> Graeme Rocher
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Grails Dev Discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [hidden email].
>> To post to this group, send email to [hidden email].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Henrique Lobo Weissmann (Kico)
> (55) 31 9226-0459
> http://devkico.itexto.com.br
> http://www.twitter.com/loboweissmann
>
> --
> You received this message because you are subscribed to the Google Groups
> "Grails Dev Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [hidden email].
> To post to this group, send email to [hidden email].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grails-dev-discuss/CAKQDOQW0adCD8HGUX5jYn9hQ2kCzAyWFkcnquq1RW6VL-YE%2BJg%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.



--
Graeme Rocher

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNoetgCZW62ey6oYczP6pOLTmnXwC7%2BBH4%3DMoA-r9_W2%3D%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

Henrique Lobo Weissmann
Graeme,

will scaffold work the same way? How will be the upgrade process for people who customized their scaffolding templates?

On Thu, Jan 29, 2015 at 6:21 PM, Graeme Rocher <[hidden email]> wrote:
Unfortunately no, but the new API is way more elegant. I hope folks
pick it up and run with it :)

On Thu, Jan 29, 2015 at 8:19 PM, Henrique Lobo Weissmann
<[hidden email]> wrote:
> Will there be any compatibility mode with previous Gant scripts?
>
> It whould help a lot of people which have customized build processes.
>
> On Thu, Jan 29, 2015 at 8:59 AM, Graeme Rocher <[hidden email]>
> wrote:
>>
>> Hi all,
>>
>> We have released Grails 3 Milestone 1 and it can be downloaded from
>> the new location at:
>>
>> https://github.com/grails/grails-core/releases/tag/v3.0.0.M1
>>
>> If you are a plugin author now is the time to consider looking at
>> porting your plugins to Grails 3.
>>
>> You can find some example plugins here:
>>
>> https://github.com/grails3-plugins/
>>
>> In particular with the code gen and build system based on Gradle some
>> plugins that interact heavily with the command line will require
>> updates.
>>
>> I have posted a video of Grails 3 in action on YouTube:
>>
>> https://www.youtube.com/watch?v=aro3_RZqgtU
>>
>> Hopefully this will get you excited to consider updating plugins. For
>> publishing we recommend publishing your plugin to Bintray. We will be
>> working on a Bintray based Grails 3 plugin portal soon. The previous
>> portal will continue for Grails 2 plugins.
>>
>> We look forward to the plugin community help drive forward Grails 3
>>
>> Thanks, and look forward to your feedback.
>>
>> --
>> Graeme Rocher
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Grails Dev Discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [hidden email].
>> To post to this group, send email to [hidden email].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Henrique Lobo Weissmann (Kico)
> (55) 31 9226-0459
> http://devkico.itexto.com.br
> http://www.twitter.com/loboweissmann
>
> --
> You received this message because you are subscribed to the Google Groups
> "Grails Dev Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [hidden email].
> To post to this group, send email to [hidden email].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grails-dev-discuss/CAKQDOQW0adCD8HGUX5jYn9hQ2kCzAyWFkcnquq1RW6VL-YE%2BJg%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.



--
Graeme Rocher

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNoetgCZW62ey6oYczP6pOLTmnXwC7%2BBH4%3DMoA-r9_W2%3D%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.



--
Henrique Lobo Weissmann (Kico)
(55) 31 9226-0459
http://devkico.itexto.com.br
http://www.twitter.com/loboweissmann

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAKQDOQUKmkJXiCD1S0frh4M%2B3uRVo23DFhgb5NTcnF20PjD%3D5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

zyro
In reply to this post by Graeme Rocher-2
hi,

nice!

asset-pipeline(-core) just introduced/fixed classpath asset resolution:
https://github.com/bertramdev/asset-pipeline/commit/7b50229aacfa69c9a639bb6281e024aa91d4f5c5
https://github.com/bertramdev/asset-pipeline-core/commit/62c77e0e0b8061aae41ade952153017582ae9dca

to make this work properly, i think for jar-builds (e.g. plugins)
grails-gradle-plugin should put the assets under jar:/META-INF/assets
instead of just jar:/assets.

does this look correct or am i perhaps missing sth?
davydotcom basically confirmed this already:
https://github.com/bertramdev/asset-pipeline/commit/7b50229aacfa69c9a639bb6281e024aa91d4f5c5#comments
grails 2.x ref.:
https://github.com/bertramdev/asset-pipeline/blob/master/scripts/_Events.groovy#L20

thanks, zyro

-------- Original Message  --------
Subject: ANN: Grails 3 Milestone 1 Released
From: Graeme Rocher <[hidden email]>
To: [hidden email]
<[hidden email]>
Date: Thu, 29 Jan 2015 11:59:55 +0100

> Hi all,
>
> We have released Grails 3 Milestone 1 and it can be downloaded from
> the new location at:
>
> https://github.com/grails/grails-core/releases/tag/v3.0.0.M1
>
> If you are a plugin author now is the time to consider looking at
> porting your plugins to Grails 3.
>
> You can find some example plugins here:
>
> https://github.com/grails3-plugins/
>
> In particular with the code gen and build system based on Gradle some
> plugins that interact heavily with the command line will require
> updates.
>
> I have posted a video of Grails 3 in action on YouTube:
>
> https://www.youtube.com/watch?v=aro3_RZqgtU
>
> Hopefully this will get you excited to consider updating plugins. For
> publishing we recommend publishing your plugin to Bintray. We will be
> working on a Bintray based Grails 3 plugin portal soon. The previous
> portal will continue for Grails 2 plugins.
>
> We look forward to the plugin community help drive forward Grails 3
>
> Thanks, and look forward to your feedback.
>

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/54CB3550.3000609%40zyro.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

Ronny Løvtangen
In reply to this post by Graeme Rocher-2
Hi,

In case others have problem opening a Grails 3 project in IntelliJ, as showed in the screencast:

On the “Import project from Gradle” dialog I got:

        Resolve error
        Cause: asset/pipeline/gradle/AssetPipelinePlugin : Unsupported major.minor version 51.0

This is due to default project SDK in IntelliJ being set to Java 6 or nothing at all, and the Gradle import dialog has as far as I can see no support for selecting SDK version for a project before importing.

To fix this:
- Close all projects
- Select: Configure —> Project Defaults —> Project Structure
- Set Java 7 or 8 as default Project SDK


Best Regards,
Ronny


> On 29 Jan 2015, at 11:59, Graeme Rocher <[hidden email]> wrote:
>
> Hi all,
>
> We have released Grails 3 Milestone 1 and it can be downloaded from
> the new location at:
>
> https://github.com/grails/grails-core/releases/tag/v3.0.0.M1
>
> If you are a plugin author now is the time to consider looking at
> porting your plugins to Grails 3.
>
> You can find some example plugins here:
>
> https://github.com/grails3-plugins/
>
> In particular with the code gen and build system based on Gradle some
> plugins that interact heavily with the command line will require
> updates.
>
> I have posted a video of Grails 3 in action on YouTube:
>
> https://www.youtube.com/watch?v=aro3_RZqgtU
>
> Hopefully this will get you excited to consider updating plugins. For
> publishing we recommend publishing your plugin to Bintray. We will be
> working on a Bintray based Grails 3 plugin portal soon. The previous
> portal will continue for Grails 2 plugins.
>
> We look forward to the plugin community help drive forward Grails 3
>
> Thanks, and look forward to your feedback.
>
> --
> Graeme Rocher
>
> --
> You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To post to this group, send email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/52247A40-EA13-4BC3-BCC7-8556D2ED1DC5%40lovtangen.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

Ronny Løvtangen
However, I was not able to run Application.main(…) from within IntelliJ. Got the following exception. Any hints? Is there some invokedynamic settings I need to perform?
Tried with JDK 1.7.0_65  and 1.8.0_11.


ERROR grails.boot.GrailsApp - Application startup failed
java.lang.VerifyError: Bad <init> method call from inside of a branch
Exception Details:
  Location:
    grails/web/mime/MimeType.<init>(Ljava/lang/String;)V @115: invokespecial
  Reason:
    Error exists in the bytecode
  Bytecode:
    0000000: 05bd 0004 5903 2b12 4fb8 009c 5359 0403
    0000010: bd00 04b8 003d 128e b800 9c53 5910 ff12
    0000020: 02b8 00a0 2a5f ab00 0000 00a2 0000 0004
    0000030: a159 6e5c 0000 002a aad3 b1ff 0000 0053
    0000040: b7d2 0ba6 0000 0066 e925 fa09 0000 0085
    0000050: 5f5a 5903 32b8 006d c000 4f5f 5904 32b8
    0000060: 006d c000 4f5f 5905 3212 8eb8 005d c000
    0000070: 8e5f 57b7 002e a700 5c5f 5a59 0332 b800
    0000080: 6dc0 004f 5f57 b700 a2a7 0049 5f5a 5903
    0000090: 32b8 006d c000 4f5f 5904 3212 8eb8 005d
    00000a0: c000 8e5f 57b7 00a4 a700 2a5f 5a59 0332
    00000b0: b800 6dc0 004f 5f59 0432 b800 6dc0 004f
    00000c0: 5f57 b700 a7a7 000d bb00 a959 12ab b700
    00000d0: acbf 57b1                              
  Stackmap Table:
    full_frame(@80,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
    full_frame(@121,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
    full_frame(@140,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
    full_frame(@171,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
    full_frame(@200,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
    full_frame(@210,{Object[#2],Object[#79]},{Object[#89]})

        at java.lang.Class.getDeclaredConstructors0(Native Method) ~[na:1.7.0_65]
        at java.lang.Class.privateGetDeclaredConstructors(Class.java:2532) ~[na:1.7.0_65]
        at java.lang.Class.getDeclaredConstructors(Class.java:1901) ~[na:1.7.0_65]
        at org.codehaus.groovy.reflection.CachedClass$2$1.run(CachedClass.java:71) ~[groovy-2.4.0.jar:2.4.0]
        at java.security.AccessController.doPrivileged(Native Method) ~[na:1.7.0_65]
        at org.codehaus.groovy.reflection.CachedClass$2.initValue(CachedClass.java:68) ~[groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.reflection.CachedClass$2.initValue(CachedClass.java:66) ~[groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.util.LazyReference.getLocked(LazyReference.java:46) ~[groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.util.LazyReference.get(LazyReference.java:33) ~[groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.reflection.CachedClass.getConstructors(CachedClass.java:265) ~[groovy-2.4.0.jar:2.4.0]
        at groovy.lang.MetaClassImpl.<init>(MetaClassImpl.java:215) ~[groovy-2.4.0.jar:2.4.0]
        at groovy.lang.MetaClassImpl.<init>(MetaClassImpl.java:225) ~[groovy-2.4.0.jar:2.4.0]
        at groovy.lang.MetaClassRegistry$MetaClassCreationHandle.createNormalMetaClass(MetaClassRegistry.java:168) ~[groovy-2.4.0.jar:2.4.0]
        at groovy.lang.MetaClassRegistry$MetaClassCreationHandle.createWithCustomLookup(MetaClassRegistry.java:158) ~[groovy-2.4.0.jar:2.4.0]
        at groovy.lang.MetaClassRegistry$MetaClassCreationHandle.create(MetaClassRegistry.java:141) ~[groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.reflection.ClassInfo.getMetaClassUnderLock(ClassInfo.java:250) ~[groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.reflection.ClassInfo.getMetaClass(ClassInfo.java:282) ~[groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.runtime.callsite.ClassMetaClassGetPropertySite.<init>(ClassMetaClassGetPropertySite.java:35) ~[groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.createClassMetaClassGetPropertySite(AbstractCallSite.java:360) [groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.createGetPropertySite(AbstractCallSite.java:312) [groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.acceptGetProperty(AbstractCallSite.java:299) [groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:291) [groovy-2.4.0.jar:2.4.0]
        at org.grails.plugins.web.mime.MimeTypesGrailsPlugin$_doWithSpring_closure1.doCall(MimeTypesGrailsPlugin.groovy:39) ~[grails-plugin-mimetypes-3.0.0.M1.jar:3.0.0.M1]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_65]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_65]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_65]
        at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_65]
        at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) [groovy-2.4.0.jar:2.4.0]
        at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324) [groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:292) ~[groovy-2.4.0.jar:2.4.0]
        at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1017) ~[groovy-2.4.0.jar:2.4.0]
        at groovy.lang.Closure.call(Closure.java:423) ~[groovy-2.4.0.jar:2.4.0]
        at groovy.lang.Closure.call(Closure.java:417) ~[groovy-2.4.0.jar:2.4.0]
        at grails.spring.BeanBuilder.invokeBeanDefiningClosure(BeanBuilder.java:754) ~[grails-spring-3.0.0.M1.jar:3.0.0.M1]
        at grails.spring.BeanBuilder.beans(BeanBuilder.java:584) ~[grails-spring-3.0.0.M1.jar:3.0.0.M1]
        at grails.spring.BeanBuilder.invokeMethod(BeanBuilder.java:527) ~[grails-spring-3.0.0.M1.jar:3.0.0.M1]
        at org.grails.plugins.DefaultGrailsPlugin.doWithRuntimeConfiguration(DefaultGrailsPlugin.java:547) ~[grails-core-3.0.0.M1.jar:3.0.0.M1]
        at org.grails.plugins.AbstractGrailsPluginManager.doRuntimeConfiguration(AbstractGrailsPluginManager.java:171) ~[grails-core-3.0.0.M1.jar:3.0.0.M1]
        at grails.boot.config.GrailsApplicationPostProcessor.postProcessBeanDefinitionRegistry(GrailsApplicationPostProcessor.groovy:78) ~[grails-core-3.0.0.M1.jar:3.0.0.M1]
        at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:119) ~[spring-context-4.1.4.RELEASE.jar:4.1.4.RELEASE]
        at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:606) ~[spring-context-4.1.4.RELEASE.jar:4.1.4.RELEASE]
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:462) ~[spring-context-4.1.4.RELEASE.jar:4.1.4.RELEASE]
        at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:118) ~[spring-boot-1.2.1.RELEASE.jar:1.2.1.RELEASE]
        at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:691) ~[spring-boot-1.2.1.RELEASE.jar:1.2.1.RELEASE]
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:321) ~[spring-boot-1.2.1.RELEASE.jar:1.2.1.RELEASE]
        at grails.boot.GrailsApp.run(GrailsApp.groovy:40) [grails-core-3.0.0.M1.jar:3.0.0.M1]
        at grails.boot.GrailsApp.run(GrailsApp.groovy:187) [grails-core-3.0.0.M1.jar:3.0.0.M1]
        at grails.boot.GrailsApp.run(GrailsApp.groovy:176) [grails-core-3.0.0.M1.jar:3.0.0.M1]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_65]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_65]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_65]
        at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_65]
        at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) [groovy-2.4.0.jar:2.4.0]
        at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324) [groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43) [groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.call(StaticMetaMethodSite.java:88) [groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) [groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) [groovy-2.4.0.jar:2.4.0]
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) [groovy-2.4.0.jar:2.4.0]
        at g300m1.Application.main(Application.groovy:8) [main/:na]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_65]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_65]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_65]
        at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_65]
        at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) [idea_rt.jar:na]


> On 30 Jan 2015, at 10:53, Ronny Løvtangen <[hidden email]> wrote:
>
> Hi,
>
> In case others have problem opening a Grails 3 project in IntelliJ, as showed in the screencast:
>
> On the “Import project from Gradle” dialog I got:
>
> Resolve error
> Cause: asset/pipeline/gradle/AssetPipelinePlugin : Unsupported major.minor version 51.0
>
> This is due to default project SDK in IntelliJ being set to Java 6 or nothing at all, and the Gradle import dialog has as far as I can see no support for selecting SDK version for a project before importing.
>
> To fix this:
> - Close all projects
> - Select: Configure —> Project Defaults —> Project Structure
> - Set Java 7 or 8 as default Project SDK
>
>
> Best Regards,
> Ronny
>
>
>> On 29 Jan 2015, at 11:59, Graeme Rocher <[hidden email]> wrote:
>>
>> Hi all,
>>
>> We have released Grails 3 Milestone 1 and it can be downloaded from
>> the new location at:
>>
>> https://github.com/grails/grails-core/releases/tag/v3.0.0.M1
>>
>> If you are a plugin author now is the time to consider looking at
>> porting your plugins to Grails 3.
>>
>> You can find some example plugins here:
>>
>> https://github.com/grails3-plugins/
>>
>> In particular with the code gen and build system based on Gradle some
>> plugins that interact heavily with the command line will require
>> updates.
>>
>> I have posted a video of Grails 3 in action on YouTube:
>>
>> https://www.youtube.com/watch?v=aro3_RZqgtU
>>
>> Hopefully this will get you excited to consider updating plugins. For
>> publishing we recommend publishing your plugin to Bintray. We will be
>> working on a Bintray based Grails 3 plugin portal soon. The previous
>> portal will continue for Grails 2 plugins.
>>
>> We look forward to the plugin community help drive forward Grails 3
>>
>> Thanks, and look forward to your feedback.
>>
>> --
>> Graeme Rocher
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>> To post to this group, send email to [hidden email].
>> To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To post to this group, send email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/52247A40-EA13-4BC3-BCC7-8556D2ED1DC5%40lovtangen.com.
> For more options, visit https://groups.google.com/d/optout.
>

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/8EB8B9EF-225D-4719-9B5E-812DBEB5D31B%40lovtangen.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

dmahapatro-2
Try JDK 1.7.0_75 (last & latest of 1.7). Also make sure JDK in classpath is mutually exclusive while toggling between versions 7 & 8.

This is highly likely to happen in OS X.

Thanks
Dhiraj Mahapatro

> On Jan 30, 2015, at 5:42 AM, Ronny Løvtangen <[hidden email]> wrote:
>
> However, I was not able to run Application.main(…) from within IntelliJ. Got the following exception. Any hints? Is there some invokedynamic settings I need to perform?
> Tried with JDK 1.7.0_65  and 1.8.0_11.
>
>
> ERROR grails.boot.GrailsApp - Application startup failed
> java.lang.VerifyError: Bad <init> method call from inside of a branch
> Exception Details:
>  Location:
>    grails/web/mime/MimeType.<init>(Ljava/lang/String;)V @115: invokespecial
>  Reason:
>    Error exists in the bytecode
>  Bytecode:
>    0000000: 05bd 0004 5903 2b12 4fb8 009c 5359 0403
>    0000010: bd00 04b8 003d 128e b800 9c53 5910 ff12
>    0000020: 02b8 00a0 2a5f ab00 0000 00a2 0000 0004
>    0000030: a159 6e5c 0000 002a aad3 b1ff 0000 0053
>    0000040: b7d2 0ba6 0000 0066 e925 fa09 0000 0085
>    0000050: 5f5a 5903 32b8 006d c000 4f5f 5904 32b8
>    0000060: 006d c000 4f5f 5905 3212 8eb8 005d c000
>    0000070: 8e5f 57b7 002e a700 5c5f 5a59 0332 b800
>    0000080: 6dc0 004f 5f57 b700 a2a7 0049 5f5a 5903
>    0000090: 32b8 006d c000 4f5f 5904 3212 8eb8 005d
>    00000a0: c000 8e5f 57b7 00a4 a700 2a5f 5a59 0332
>    00000b0: b800 6dc0 004f 5f59 0432 b800 6dc0 004f
>    00000c0: 5f57 b700 a7a7 000d bb00 a959 12ab b700
>    00000d0: acbf 57b1                              
>  Stackmap Table:
>    full_frame(@80,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
>    full_frame(@121,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
>    full_frame(@140,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
>    full_frame(@171,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
>    full_frame(@200,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
>    full_frame(@210,{Object[#2],Object[#79]},{Object[#89]})
>
>    at java.lang.Class.getDeclaredConstructors0(Native Method) ~[na:1.7.0_65]
>    at java.lang.Class.privateGetDeclaredConstructors(Class.java:2532) ~[na:1.7.0_65]
>    at java.lang.Class.getDeclaredConstructors(Class.java:1901) ~[na:1.7.0_65]
>    at org.codehaus.groovy.reflection.CachedClass$2$1.run(CachedClass.java:71) ~[groovy-2.4.0.jar:2.4.0]
>    at java.security.AccessController.doPrivileged(Native Method) ~[na:1.7.0_65]
>    at org.codehaus.groovy.reflection.CachedClass$2.initValue(CachedClass.java:68) ~[groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.reflection.CachedClass$2.initValue(CachedClass.java:66) ~[groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.util.LazyReference.getLocked(LazyReference.java:46) ~[groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.util.LazyReference.get(LazyReference.java:33) ~[groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.reflection.CachedClass.getConstructors(CachedClass.java:265) ~[groovy-2.4.0.jar:2.4.0]
>    at groovy.lang.MetaClassImpl.<init>(MetaClassImpl.java:215) ~[groovy-2.4.0.jar:2.4.0]
>    at groovy.lang.MetaClassImpl.<init>(MetaClassImpl.java:225) ~[groovy-2.4.0.jar:2.4.0]
>    at groovy.lang.MetaClassRegistry$MetaClassCreationHandle.createNormalMetaClass(MetaClassRegistry.java:168) ~[groovy-2.4.0.jar:2.4.0]
>    at groovy.lang.MetaClassRegistry$MetaClassCreationHandle.createWithCustomLookup(MetaClassRegistry.java:158) ~[groovy-2.4.0.jar:2.4.0]
>    at groovy.lang.MetaClassRegistry$MetaClassCreationHandle.create(MetaClassRegistry.java:141) ~[groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.reflection.ClassInfo.getMetaClassUnderLock(ClassInfo.java:250) ~[groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.reflection.ClassInfo.getMetaClass(ClassInfo.java:282) ~[groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.runtime.callsite.ClassMetaClassGetPropertySite.<init>(ClassMetaClassGetPropertySite.java:35) ~[groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.createClassMetaClassGetPropertySite(AbstractCallSite.java:360) [groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.createGetPropertySite(AbstractCallSite.java:312) [groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.acceptGetProperty(AbstractCallSite.java:299) [groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:291) [groovy-2.4.0.jar:2.4.0]
>    at org.grails.plugins.web.mime.MimeTypesGrailsPlugin$_doWithSpring_closure1.doCall(MimeTypesGrailsPlugin.groovy:39) ~[grails-plugin-mimetypes-3.0.0.M1.jar:3.0.0.M1]
>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_65]
>    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_65]
>    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_65]
>    at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_65]
>    at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) [groovy-2.4.0.jar:2.4.0]
>    at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324) [groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:292) ~[groovy-2.4.0.jar:2.4.0]
>    at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1017) ~[groovy-2.4.0.jar:2.4.0]
>    at groovy.lang.Closure.call(Closure.java:423) ~[groovy-2.4.0.jar:2.4.0]
>    at groovy.lang.Closure.call(Closure.java:417) ~[groovy-2.4.0.jar:2.4.0]
>    at grails.spring.BeanBuilder.invokeBeanDefiningClosure(BeanBuilder.java:754) ~[grails-spring-3.0.0.M1.jar:3.0.0.M1]
>    at grails.spring.BeanBuilder.beans(BeanBuilder.java:584) ~[grails-spring-3.0.0.M1.jar:3.0.0.M1]
>    at grails.spring.BeanBuilder.invokeMethod(BeanBuilder.java:527) ~[grails-spring-3.0.0.M1.jar:3.0.0.M1]
>    at org.grails.plugins.DefaultGrailsPlugin.doWithRuntimeConfiguration(DefaultGrailsPlugin.java:547) ~[grails-core-3.0.0.M1.jar:3.0.0.M1]
>    at org.grails.plugins.AbstractGrailsPluginManager.doRuntimeConfiguration(AbstractGrailsPluginManager.java:171) ~[grails-core-3.0.0.M1.jar:3.0.0.M1]
>    at grails.boot.config.GrailsApplicationPostProcessor.postProcessBeanDefinitionRegistry(GrailsApplicationPostProcessor.groovy:78) ~[grails-core-3.0.0.M1.jar:3.0.0.M1]
>    at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:119) ~[spring-context-4.1.4.RELEASE.jar:4.1.4.RELEASE]
>    at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:606) ~[spring-context-4.1.4.RELEASE.jar:4.1.4.RELEASE]
>    at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:462) ~[spring-context-4.1.4.RELEASE.jar:4.1.4.RELEASE]
>    at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:118) ~[spring-boot-1.2.1.RELEASE.jar:1.2.1.RELEASE]
>    at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:691) ~[spring-boot-1.2.1.RELEASE.jar:1.2.1.RELEASE]
>    at org.springframework.boot.SpringApplication.run(SpringApplication.java:321) ~[spring-boot-1.2.1.RELEASE.jar:1.2.1.RELEASE]
>    at grails.boot.GrailsApp.run(GrailsApp.groovy:40) [grails-core-3.0.0.M1.jar:3.0.0.M1]
>    at grails.boot.GrailsApp.run(GrailsApp.groovy:187) [grails-core-3.0.0.M1.jar:3.0.0.M1]
>    at grails.boot.GrailsApp.run(GrailsApp.groovy:176) [grails-core-3.0.0.M1.jar:3.0.0.M1]
>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_65]
>    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_65]
>    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_65]
>    at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_65]
>    at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) [groovy-2.4.0.jar:2.4.0]
>    at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324) [groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43) [groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.call(StaticMetaMethodSite.java:88) [groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) [groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) [groovy-2.4.0.jar:2.4.0]
>    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) [groovy-2.4.0.jar:2.4.0]
>    at g300m1.Application.main(Application.groovy:8) [main/:na]
>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_65]
>    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_65]
>    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_65]
>    at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_65]
>    at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) [idea_rt.jar:na]
>
>
>> On 30 Jan 2015, at 10:53, Ronny Løvtangen <[hidden email]> wrote:
>>
>> Hi,
>>
>> In case others have problem opening a Grails 3 project in IntelliJ, as showed in the screencast:
>>
>> On the “Import project from Gradle” dialog I got:
>>
>>    Resolve error
>>    Cause: asset/pipeline/gradle/AssetPipelinePlugin : Unsupported major.minor version 51.0
>>
>> This is due to default project SDK in IntelliJ being set to Java 6 or nothing at all, and the Gradle import dialog has as far as I can see no support for selecting SDK version for a project before importing.
>>
>> To fix this:
>> - Close all projects
>> - Select: Configure —> Project Defaults —> Project Structure
>> - Set Java 7 or 8 as default Project SDK
>>
>>
>> Best Regards,
>> Ronny
>>
>>
>>> On 29 Jan 2015, at 11:59, Graeme Rocher <[hidden email]> wrote:
>>>
>>> Hi all,
>>>
>>> We have released Grails 3 Milestone 1 and it can be downloaded from
>>> the new location at:
>>>
>>> https://github.com/grails/grails-core/releases/tag/v3.0.0.M1
>>>
>>> If you are a plugin author now is the time to consider looking at
>>> porting your plugins to Grails 3.
>>>
>>> You can find some example plugins here:
>>>
>>> https://github.com/grails3-plugins/
>>>
>>> In particular with the code gen and build system based on Gradle some
>>> plugins that interact heavily with the command line will require
>>> updates.
>>>
>>> I have posted a video of Grails 3 in action on YouTube:
>>>
>>> https://www.youtube.com/watch?v=aro3_RZqgtU
>>>
>>> Hopefully this will get you excited to consider updating plugins. For
>>> publishing we recommend publishing your plugin to Bintray. We will be
>>> working on a Bintray based Grails 3 plugin portal soon. The previous
>>> portal will continue for Grails 2 plugins.
>>>
>>> We look forward to the plugin community help drive forward Grails 3
>>>
>>> Thanks, and look forward to your feedback.
>>>
>>> --
>>> Graeme Rocher
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>>> To post to this group, send email to [hidden email].
>>> To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>> To post to this group, send email to [hidden email].
>> To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/52247A40-EA13-4BC3-BCC7-8556D2ED1DC5%40lovtangen.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To post to this group, send email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/8EB8B9EF-225D-4719-9B5E-812DBEB5D31B%40lovtangen.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/48ACC360-C8D1-4D63-9EBC-95C31316A5E0%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

Ronny Løvtangen
Thanks, Dhiraj.
Both 1.7.0_75 and 1.8.0_31 worked fine :)

Ronny

> On 30 Jan 2015, at 12:10, Dhiraj Mahapatro <[hidden email]> wrote:
>
> Try JDK 1.7.0_75 (last & latest of 1.7). Also make sure JDK in classpath is mutually exclusive while toggling between versions 7 & 8.
>
> This is highly likely to happen in OS X.
>
> Thanks
> Dhiraj Mahapatro
>
>> On Jan 30, 2015, at 5:42 AM, Ronny Løvtangen <[hidden email]> wrote:
>>
>> However, I was not able to run Application.main(…) from within IntelliJ. Got the following exception. Any hints? Is there some invokedynamic settings I need to perform?
>> Tried with JDK 1.7.0_65  and 1.8.0_11.
>>
>>
>> ERROR grails.boot.GrailsApp - Application startup failed
>> java.lang.VerifyError: Bad <init> method call from inside of a branch
>> Exception Details:
>> Location:
>>   grails/web/mime/MimeType.<init>(Ljava/lang/String;)V @115: invokespecial
>> Reason:
>>   Error exists in the bytecode
>> Bytecode:
>>   0000000: 05bd 0004 5903 2b12 4fb8 009c 5359 0403
>>   0000010: bd00 04b8 003d 128e b800 9c53 5910 ff12
>>   0000020: 02b8 00a0 2a5f ab00 0000 00a2 0000 0004
>>   0000030: a159 6e5c 0000 002a aad3 b1ff 0000 0053
>>   0000040: b7d2 0ba6 0000 0066 e925 fa09 0000 0085
>>   0000050: 5f5a 5903 32b8 006d c000 4f5f 5904 32b8
>>   0000060: 006d c000 4f5f 5905 3212 8eb8 005d c000
>>   0000070: 8e5f 57b7 002e a700 5c5f 5a59 0332 b800
>>   0000080: 6dc0 004f 5f57 b700 a2a7 0049 5f5a 5903
>>   0000090: 32b8 006d c000 4f5f 5904 3212 8eb8 005d
>>   00000a0: c000 8e5f 57b7 00a4 a700 2a5f 5a59 0332
>>   00000b0: b800 6dc0 004f 5f59 0432 b800 6dc0 004f
>>   00000c0: 5f57 b700 a7a7 000d bb00 a959 12ab b700
>>   00000d0: acbf 57b1                              
>> Stackmap Table:
>>   full_frame(@80,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
>>   full_frame(@121,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
>>   full_frame(@140,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
>>   full_frame(@171,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
>>   full_frame(@200,{UninitializedThis,Object[#79]},{Object[#89],UninitializedThis})
>>   full_frame(@210,{Object[#2],Object[#79]},{Object[#89]})
>>
>>   at java.lang.Class.getDeclaredConstructors0(Native Method) ~[na:1.7.0_65]
>>   at java.lang.Class.privateGetDeclaredConstructors(Class.java:2532) ~[na:1.7.0_65]
>>   at java.lang.Class.getDeclaredConstructors(Class.java:1901) ~[na:1.7.0_65]
>>   at org.codehaus.groovy.reflection.CachedClass$2$1.run(CachedClass.java:71) ~[groovy-2.4.0.jar:2.4.0]
>>   at java.security.AccessController.doPrivileged(Native Method) ~[na:1.7.0_65]
>>   at org.codehaus.groovy.reflection.CachedClass$2.initValue(CachedClass.java:68) ~[groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.reflection.CachedClass$2.initValue(CachedClass.java:66) ~[groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.util.LazyReference.getLocked(LazyReference.java:46) ~[groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.util.LazyReference.get(LazyReference.java:33) ~[groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.reflection.CachedClass.getConstructors(CachedClass.java:265) ~[groovy-2.4.0.jar:2.4.0]
>>   at groovy.lang.MetaClassImpl.<init>(MetaClassImpl.java:215) ~[groovy-2.4.0.jar:2.4.0]
>>   at groovy.lang.MetaClassImpl.<init>(MetaClassImpl.java:225) ~[groovy-2.4.0.jar:2.4.0]
>>   at groovy.lang.MetaClassRegistry$MetaClassCreationHandle.createNormalMetaClass(MetaClassRegistry.java:168) ~[groovy-2.4.0.jar:2.4.0]
>>   at groovy.lang.MetaClassRegistry$MetaClassCreationHandle.createWithCustomLookup(MetaClassRegistry.java:158) ~[groovy-2.4.0.jar:2.4.0]
>>   at groovy.lang.MetaClassRegistry$MetaClassCreationHandle.create(MetaClassRegistry.java:141) ~[groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.reflection.ClassInfo.getMetaClassUnderLock(ClassInfo.java:250) ~[groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.reflection.ClassInfo.getMetaClass(ClassInfo.java:282) ~[groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.runtime.callsite.ClassMetaClassGetPropertySite.<init>(ClassMetaClassGetPropertySite.java:35) ~[groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.runtime.callsite.AbstractCallSite.createClassMetaClassGetPropertySite(AbstractCallSite.java:360) [groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.runtime.callsite.AbstractCallSite.createGetPropertySite(AbstractCallSite.java:312) [groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.runtime.callsite.AbstractCallSite.acceptGetProperty(AbstractCallSite.java:299) [groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:291) [groovy-2.4.0.jar:2.4.0]
>>   at org.grails.plugins.web.mime.MimeTypesGrailsPlugin$_doWithSpring_closure1.doCall(MimeTypesGrailsPlugin.groovy:39) ~[grails-plugin-mimetypes-3.0.0.M1.jar:3.0.0.M1]
>>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_65]
>>   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_65]
>>   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_65]
>>   at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_65]
>>   at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) [groovy-2.4.0.jar:2.4.0]
>>   at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324) [groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:292) ~[groovy-2.4.0.jar:2.4.0]
>>   at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1017) ~[groovy-2.4.0.jar:2.4.0]
>>   at groovy.lang.Closure.call(Closure.java:423) ~[groovy-2.4.0.jar:2.4.0]
>>   at groovy.lang.Closure.call(Closure.java:417) ~[groovy-2.4.0.jar:2.4.0]
>>   at grails.spring.BeanBuilder.invokeBeanDefiningClosure(BeanBuilder.java:754) ~[grails-spring-3.0.0.M1.jar:3.0.0.M1]
>>   at grails.spring.BeanBuilder.beans(BeanBuilder.java:584) ~[grails-spring-3.0.0.M1.jar:3.0.0.M1]
>>   at grails.spring.BeanBuilder.invokeMethod(BeanBuilder.java:527) ~[grails-spring-3.0.0.M1.jar:3.0.0.M1]
>>   at org.grails.plugins.DefaultGrailsPlugin.doWithRuntimeConfiguration(DefaultGrailsPlugin.java:547) ~[grails-core-3.0.0.M1.jar:3.0.0.M1]
>>   at org.grails.plugins.AbstractGrailsPluginManager.doRuntimeConfiguration(AbstractGrailsPluginManager.java:171) ~[grails-core-3.0.0.M1.jar:3.0.0.M1]
>>   at grails.boot.config.GrailsApplicationPostProcessor.postProcessBeanDefinitionRegistry(GrailsApplicationPostProcessor.groovy:78) ~[grails-core-3.0.0.M1.jar:3.0.0.M1]
>>   at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:119) ~[spring-context-4.1.4.RELEASE.jar:4.1.4.RELEASE]
>>   at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:606) ~[spring-context-4.1.4.RELEASE.jar:4.1.4.RELEASE]
>>   at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:462) ~[spring-context-4.1.4.RELEASE.jar:4.1.4.RELEASE]
>>   at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:118) ~[spring-boot-1.2.1.RELEASE.jar:1.2.1.RELEASE]
>>   at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:691) ~[spring-boot-1.2.1.RELEASE.jar:1.2.1.RELEASE]
>>   at org.springframework.boot.SpringApplication.run(SpringApplication.java:321) ~[spring-boot-1.2.1.RELEASE.jar:1.2.1.RELEASE]
>>   at grails.boot.GrailsApp.run(GrailsApp.groovy:40) [grails-core-3.0.0.M1.jar:3.0.0.M1]
>>   at grails.boot.GrailsApp.run(GrailsApp.groovy:187) [grails-core-3.0.0.M1.jar:3.0.0.M1]
>>   at grails.boot.GrailsApp.run(GrailsApp.groovy:176) [grails-core-3.0.0.M1.jar:3.0.0.M1]
>>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_65]
>>   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_65]
>>   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_65]
>>   at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_65]
>>   at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) [groovy-2.4.0.jar:2.4.0]
>>   at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:324) [groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43) [groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.call(StaticMetaMethodSite.java:88) [groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:45) [groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) [groovy-2.4.0.jar:2.4.0]
>>   at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) [groovy-2.4.0.jar:2.4.0]
>>   at g300m1.Application.main(Application.groovy:8) [main/:na]
>>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_65]
>>   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_65]
>>   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_65]
>>   at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_65]
>>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) [idea_rt.jar:na]
>>
>>
>>> On 30 Jan 2015, at 10:53, Ronny Løvtangen <[hidden email]> wrote:
>>>
>>> Hi,
>>>
>>> In case others have problem opening a Grails 3 project in IntelliJ, as showed in the screencast:
>>>
>>> On the “Import project from Gradle” dialog I got:
>>>
>>>   Resolve error
>>>   Cause: asset/pipeline/gradle/AssetPipelinePlugin : Unsupported major.minor version 51.0
>>>
>>> This is due to default project SDK in IntelliJ being set to Java 6 or nothing at all, and the Gradle import dialog has as far as I can see no support for selecting SDK version for a project before importing.
>>>
>>> To fix this:
>>> - Close all projects
>>> - Select: Configure —> Project Defaults —> Project Structure
>>> - Set Java 7 or 8 as default Project SDK
>>>
>>>
>>> Best Regards,
>>> Ronny
>>>
>>>
>>>> On 29 Jan 2015, at 11:59, Graeme Rocher <[hidden email]> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> We have released Grails 3 Milestone 1 and it can be downloaded from
>>>> the new location at:
>>>>
>>>> https://github.com/grails/grails-core/releases/tag/v3.0.0.M1
>>>>
>>>> If you are a plugin author now is the time to consider looking at
>>>> porting your plugins to Grails 3.
>>>>
>>>> You can find some example plugins here:
>>>>
>>>> https://github.com/grails3-plugins/
>>>>
>>>> In particular with the code gen and build system based on Gradle some
>>>> plugins that interact heavily with the command line will require
>>>> updates.
>>>>
>>>> I have posted a video of Grails 3 in action on YouTube:
>>>>
>>>> https://www.youtube.com/watch?v=aro3_RZqgtU
>>>>
>>>> Hopefully this will get you excited to consider updating plugins. For
>>>> publishing we recommend publishing your plugin to Bintray. We will be
>>>> working on a Bintray based Grails 3 plugin portal soon. The previous
>>>> portal will continue for Grails 2 plugins.
>>>>
>>>> We look forward to the plugin community help drive forward Grails 3
>>>>
>>>> Thanks, and look forward to your feedback.
>>>>
>>>> --
>>>> Graeme Rocher
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>>>> To post to this group, send email to [hidden email].
>>>> To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>>> To post to this group, send email to [hidden email].
>>> To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/52247A40-EA13-4BC3-BCC7-8556D2ED1DC5%40lovtangen.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>> To post to this group, send email to [hidden email].
>> To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/8EB8B9EF-225D-4719-9B5E-812DBEB5D31B%40lovtangen.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To post to this group, send email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/48ACC360-C8D1-4D63-9EBC-95C31316A5E0%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/8CB62318-C8BE-44EF-98F1-A7AEC9F61BBD%40lovtangen.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

Tamer
In reply to this post by Graeme Rocher-2
Superb!

I can't wait to try it! I'll save some time this week end for this :)

Thanks for all your work guys..

Grails rocks!
:)
Il giorno giovedì 29 gennaio 2015 11:00:16 UTC, Graeme Rocher ha scritto:
Hi all,

We have released Grails 3 Milestone 1 and it can be downloaded from
the new location at:

<a href="https://github.com/grails/grails-core/releases/tag/v3.0.0.M1" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Freleases%2Ftag%2Fv3.0.0.M1\46sa\75D\46sntz\0751\46usg\75AFQjCNE8DuRc-U9sniBXV4R5liIL37cqJA';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Freleases%2Ftag%2Fv3.0.0.M1\46sa\75D\46sntz\0751\46usg\75AFQjCNE8DuRc-U9sniBXV4R5liIL37cqJA';return true;">https://github.com/grails/grails-core/releases/tag/v3.0.0.M1

If you are a plugin author now is the time to consider looking at
porting your plugins to Grails 3.

You can find some example plugins here:

<a href="https://github.com/grails3-plugins/" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails3-plugins%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNHNOojpI3eMW8odZ4K-YNTFpNdX9g';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails3-plugins%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNHNOojpI3eMW8odZ4K-YNTFpNdX9g';return true;">https://github.com/grails3-plugins/

In particular with the code gen and build system based on Gradle some
plugins that interact heavily with the command line will require
updates.

I have posted a video of Grails 3 in action on YouTube:

<a href="https://www.youtube.com/watch?v=aro3_RZqgtU" target="_blank" rel="nofollow" onmousedown="this.href='https://www.youtube.com/watch?v\75aro3_RZqgtU';return true;" onclick="this.href='https://www.youtube.com/watch?v\75aro3_RZqgtU';return true;">https://www.youtube.com/watch?v=aro3_RZqgtU

Hopefully this will get you excited to consider updating plugins. For
publishing we recommend publishing your plugin to Bintray. We will be
working on a Bintray based Grails 3 plugin portal soon. The previous
portal will continue for Grails 2 plugins.

We look forward to the plugin community help drive forward Grails 3

Thanks, and look forward to your feedback.

--
Graeme Rocher

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/5133b521-50a6-4e90-b547-03682dbd6e79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

sergiomichels
Cool! Nice to see Grails using Gradle :-)

--
Sérgio Michels

On Fri, Jan 30, 2015 at 10:02 AM, Tamer Shahin <[hidden email]> wrote:
Superb!

I can't wait to try it! I'll save some time this week end for this :)

Thanks for all your work guys..

Grails rocks!
:)
Il giorno giovedì 29 gennaio 2015 11:00:16 UTC, Graeme Rocher ha scritto:
Hi all,

We have released Grails 3 Milestone 1 and it can be downloaded from
the new location at:

https://github.com/grails/grails-core/releases/tag/v3.0.0.M1

If you are a plugin author now is the time to consider looking at
porting your plugins to Grails 3.

You can find some example plugins here:

https://github.com/grails3-plugins/

In particular with the code gen and build system based on Gradle some
plugins that interact heavily with the command line will require
updates.

I have posted a video of Grails 3 in action on YouTube:

https://www.youtube.com/watch?v=aro3_RZqgtU

Hopefully this will get you excited to consider updating plugins. For
publishing we recommend publishing your plugin to Bintray. We will be
working on a Bintray based Grails 3 plugin portal soon. The previous
portal will continue for Grails 2 plugins.

We look forward to the plugin community help drive forward Grails 3

Thanks, and look forward to your feedback.

--
Graeme Rocher

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/5133b521-50a6-4e90-b547-03682dbd6e79%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAHTf1NUWMsnXvNBQVw%3D-OiQ%2BLJkUc%2BmNpR3mAqM5FBer0JEWsA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

d.tamm
This post has NOT been accepted by the mailing list yet.
In reply to this post by Graeme Rocher-2
Finally, i have been waiting for this :) thanks graeme!

Graeme: can you point out if there is a performance improvement between grails 2 and grails 3? i was just wondering because i use grails 2.4.4 for my office project, which got quite big lately and will grow in the near future (124 controllers, 170 domain classes, 65 services, using 5 plugins atm, including the quartz plugin with 9 jobs) and i recently had troubles with starting the application from netbeans (behaving extremly slow and getting fast to permgen space errors).
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

Benoit HEDIARD
In reply to this post by Graeme Rocher-2
It looks awesome, thanks Graeme !
Looking forward to migrate our plugins.

Do you want us to start reporting bugs?

It looks like, current 'grails package' does not support parent folder name with a dash:

Execution failed for task ':compileGroovyPages'.

> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:

  /Users/ben/Documents/Projects/grails/test-grails3/build/gsptmp/gsp_test-grails3error_gsp.groovy: 8: unexpected token: - @ line 8, column 15.

     class gsp_test-grails3error_gsp extends GroovyPage {


When renaming the parent project from test-grails3 to test_grails3, it works fine.

Le jeudi 29 janvier 2015 12:00:16 UTC+1, Graeme Rocher a écrit :
Hi all,

We have released Grails 3 Milestone 1 and it can be downloaded from
the new location at:

<a href="https://github.com/grails/grails-core/releases/tag/v3.0.0.M1" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Freleases%2Ftag%2Fv3.0.0.M1\46sa\75D\46sntz\0751\46usg\75AFQjCNE8DuRc-U9sniBXV4R5liIL37cqJA';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Freleases%2Ftag%2Fv3.0.0.M1\46sa\75D\46sntz\0751\46usg\75AFQjCNE8DuRc-U9sniBXV4R5liIL37cqJA';return true;">https://github.com/grails/grails-core/releases/tag/v3.0.0.M1

If you are a plugin author now is the time to consider looking at
porting your plugins to Grails 3.

You can find some example plugins here:

<a href="https://github.com/grails3-plugins/" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails3-plugins%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNHNOojpI3eMW8odZ4K-YNTFpNdX9g';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails3-plugins%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNHNOojpI3eMW8odZ4K-YNTFpNdX9g';return true;">https://github.com/grails3-plugins/

In particular with the code gen and build system based on Gradle some
plugins that interact heavily with the command line will require
updates.

I have posted a video of Grails 3 in action on YouTube:

<a href="https://www.youtube.com/watch?v=aro3_RZqgtU" target="_blank" rel="nofollow" onmousedown="this.href='https://www.youtube.com/watch?v\75aro3_RZqgtU';return true;" onclick="this.href='https://www.youtube.com/watch?v\75aro3_RZqgtU';return true;">https://www.youtube.com/watch?v=aro3_RZqgtU

Hopefully this will get you excited to consider updating plugins. For
publishing we recommend publishing your plugin to Bintray. We will be
working on a Bintray based Grails 3 plugin portal soon. The previous
portal will continue for Grails 2 plugins.

We look forward to the plugin community help drive forward Grails 3

Thanks, and look forward to your feedback.

--
Graeme Rocher

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/cc1f721c-a94b-41e5-adea-d39e29e0e1e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

dmahapatro-2

Dhiraj

On Sat, Jan 31, 2015 at 5:40 AM, Benoit Hediard <[hidden email]> wrote:
It looks awesome, thanks Graeme !
Looking forward to migrate our plugins.

Do you want us to start reporting bugs?

It looks like, current 'grails package' does not support parent folder name with a dash:

Execution failed for task ':compileGroovyPages'.

> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:

  /Users/ben/Documents/Projects/grails/test-grails3/build/gsptmp/gsp_test-grails3error_gsp.groovy: 8: unexpected token: - @ line 8, column 15.

     class gsp_test-grails3error_gsp extends GroovyPage {


When renaming the parent project from test-grails3 to test_grails3, it works fine.

Le jeudi 29 janvier 2015 12:00:16 UTC+1, Graeme Rocher a écrit :
Hi all,

We have released Grails 3 Milestone 1 and it can be downloaded from
the new location at:

https://github.com/grails/grails-core/releases/tag/v3.0.0.M1

If you are a plugin author now is the time to consider looking at
porting your plugins to Grails 3.

You can find some example plugins here:

https://github.com/grails3-plugins/

In particular with the code gen and build system based on Gradle some
plugins that interact heavily with the command line will require
updates.

I have posted a video of Grails 3 in action on YouTube:

https://www.youtube.com/watch?v=aro3_RZqgtU

Hopefully this will get you excited to consider updating plugins. For
publishing we recommend publishing your plugin to Bintray. We will be
working on a Bintray based Grails 3 plugin portal soon. The previous
portal will continue for Grails 2 plugins.

We look forward to the plugin community help drive forward Grails 3

Thanks, and look forward to your feedback.

--
Graeme Rocher

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/cc1f721c-a94b-41e5-adea-d39e29e0e1e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/CAAodtxBJLS8ZF3N9fSd2n5OQhxEViRTctZkxhEi5Pg2Vs_gJWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Grails 3 Milestone 1 Released

olavgg
In reply to this post by Ronny Løvtangen
Thank you! I was so confused when I saw this error, glad to see this solution!

fredag 30. januar 2015 04.54.00 UTC-5 skrev Ronny Løvtangen følgende:
Hi,

In case others have problem opening a Grails 3 project in IntelliJ, as showed in the screencast:

On the “Import project from Gradle” dialog I got:

        Resolve error
        Cause: asset/pipeline/gradle/AssetPipelinePlugin : Unsupported major.minor version 51.0

This is due to default project SDK in IntelliJ being set to Java 6 or nothing at all, and the Gradle import dialog has as far as I can see no support for selecting SDK version for a project before importing.

To fix this:
- Close all projects
- Select: Configure —> Project Defaults —> Project Structure
- Set Java 7 or 8 as default Project SDK


Best Regards,
Ronny


> On 29 Jan 2015, at 11:59, Graeme Rocher <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="d1VuH1vr2EwJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">graeme...@...> wrote:
>
> Hi all,
>
> We have released Grails 3 Milestone 1 and it can be downloaded from
> the new location at:
>
> <a href="https://github.com/grails/grails-core/releases/tag/v3.0.0.M1" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Freleases%2Ftag%2Fv3.0.0.M1\46sa\75D\46sntz\0751\46usg\75AFQjCNE8DuRc-U9sniBXV4R5liIL37cqJA';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails%2Fgrails-core%2Freleases%2Ftag%2Fv3.0.0.M1\46sa\75D\46sntz\0751\46usg\75AFQjCNE8DuRc-U9sniBXV4R5liIL37cqJA';return true;">https://github.com/grails/grails-core/releases/tag/v3.0.0.M1
>
> If you are a plugin author now is the time to consider looking at
> porting your plugins to Grails 3.
>
> You can find some example plugins here:
>
> <a href="https://github.com/grails3-plugins/" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails3-plugins%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNHNOojpI3eMW8odZ4K-YNTFpNdX9g';return true;" onclick="this.href='https://www.google.com/url?q\75https%3A%2F%2Fgithub.com%2Fgrails3-plugins%2F\46sa\75D\46sntz\0751\46usg\75AFQjCNHNOojpI3eMW8odZ4K-YNTFpNdX9g';return true;">https://github.com/grails3-plugins/
>
> In particular with the code gen and build system based on Gradle some
> plugins that interact heavily with the command line will require
> updates.
>
> I have posted a video of Grails 3 in action on YouTube:
>
> <a href="https://www.youtube.com/watch?v=aro3_RZqgtU" target="_blank" rel="nofollow" onmousedown="this.href='https://www.youtube.com/watch?v\75aro3_RZqgtU';return true;" onclick="this.href='https://www.youtube.com/watch?v\75aro3_RZqgtU';return true;">https://www.youtube.com/watch?v=aro3_RZqgtU
>
> Hopefully this will get you excited to consider updating plugins. For
> publishing we recommend publishing your plugin to Bintray. We will be
> working on a Bintray based Grails 3 plugin portal soon. The previous
> portal will continue for Grails 2 plugins.
>
> We look forward to the plugin community help drive forward Grails 3
>
> Thanks, and look forward to your feedback.
>
> --
> Graeme Rocher
>
> --
> You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="d1VuH1vr2EwJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">grails-dev-discuss+unsubscribe@....
> To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="d1VuH1vr2EwJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">grails-de...@googlegroups.com.
> To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com" target="_blank" rel="nofollow" onmousedown="this.href='https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com';return true;" onclick="this.href='https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com';return true;">https://groups.google.com/d/msgid/grails-dev-discuss/CAO_wNocWXpzBQQxMgbwj_OxAQ_Ab4hvKb7ndvbvLZHe4R6SNKA%40mail.gmail.com.
> For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href='https://groups.google.com/d/optout';return true;" onclick="this.href='https://groups.google.com/d/optout';return true;">https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/7da517b5-182b-4f59-8b75-7bf7a922c17e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.