Grails 3.0 and Yaml why? Is something gained by it or is it a time constraint reason?

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

Grails 3.0 and Yaml why? Is something gained by it or is it a time constraint reason?

virtualdogbert
So I've noticed that Grails 3.0 uses Yaml for configuration, and I have several questions around it:

Why Yaml, just because it seem to be Spring Boots default?

Is there any gain, or advantage of yaml over Groovy based configuration?

Is this decision more of a time based thing? 

it seems with Pivotal's decision Grails 3.0 is a little rushed out the door, especially considering discussed time lines during springone 2gx. Is this something that maybe revisited?

I know that you can use Groovy in place of the yaml. Is there any down side?

Will there be a profile with Groovy configuration?

Thank you if  you have time to answer this. Over all Grails 3.0 looks like it's going to be another great leap forward, despite the fight I know I'm going to have upgrading to it.

--
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/1b4fa638-8a49-4a1f-baba-0ec72215ddd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Grails 3.0 and Yaml why? Is something gained by it or is it a time constraint reason?

Graeme Rocher-2
It has nothing to do with being rushed. Quite simply we wanted a format that is machine readable AND writable to be the default. You cannot programmatically write to the Groovy format. However if you prefer the Groovy format you can still use it by creating a application.groovy file 

On Friday, March 13, 2015, virtual dogbert <[hidden email]> wrote:
So I've noticed that Grails 3.0 uses Yaml for configuration, and I have several questions around it:

Why Yaml, just because it seem to be Spring Boots default?

Is there any gain, or advantage of yaml over Groovy based configuration?

Is this decision more of a time based thing? 

it seems with Pivotal's decision Grails 3.0 is a little rushed out the door, especially considering discussed time lines during springone 2gx. Is this something that maybe revisited?

I know that you can use Groovy in place of the yaml. Is there any down side?

Will there be a profile with Groovy configuration?

Thank you if  you have time to answer this. Over all Grails 3.0 looks like it's going to be another great leap forward, despite the fight I know I'm going to have upgrading to it.

--
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:_e(%7B%7D,&#39;cvml&#39;,&#39;grails-dev-discuss%2Bunsubscribe@googlegroups.com&#39;);" target="_blank">grails-dev-discuss+unsubscribe@....
To post to this group, send email to <a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;grails-dev-discuss@googlegroups.com&#39;);" target="_blank">grails-dev-discuss@....
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/1b4fa638-8a49-4a1f-baba-0ec72215ddd8%40googlegroups.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_wNod2F0UG6TtWLJ7CRCFTCcYuALY8yVAOAxbD_xfHPSKJTQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Grails 3.0 and Yaml why? Is something gained by it or is it a time constraint reason?

Henrique Lobo Weissmann
In reply to this post by virtualdogbert
What about the DataSources.groovy file? Will it be removed too?

On Fri, Mar 13, 2015 at 12:33 AM, virtual dogbert <[hidden email]> wrote:
So I've noticed that Grails 3.0 uses Yaml for configuration, and I have several questions around it:

Why Yaml, just because it seem to be Spring Boots default?

Is there any gain, or advantage of yaml over Groovy based configuration?

Is this decision more of a time based thing? 

it seems with Pivotal's decision Grails 3.0 is a little rushed out the door, especially considering discussed time lines during springone 2gx. Is this something that maybe revisited?

I know that you can use Groovy in place of the yaml. Is there any down side?

Will there be a profile with Groovy configuration?

Thank you if  you have time to answer this. Over all Grails 3.0 looks like it's going to be another great leap forward, despite the fight I know I'm going to have upgrading to it.

--
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/1b4fa638-8a49-4a1f-baba-0ec72215ddd8%40googlegroups.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/CAKQDOQXQKRydFwZn705ckq-xXyOK_5KaTwg3ZmaWrH4reJXU_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Grails 3.0 and Yaml why? Is something gained by it or is it a time constraint reason?

virtualdogbert
"The configuration of the application will need to be migrated, this can normally be done by simply renaming grails-app/conf/Config.groovy to grails-app/conf/application.groovy and merging the content of grails-app/conf/DataSource.groovy into grails-app/conf/application.groovy." from http://grails.github.io/grails-doc/3.0.x/guide/single.html#upgradingApps

Which puts potentially a lot of configuration in one file, that doesn't nesesarily go together.  So hopefully there is a way to split up config files like before:
http://stackoverflow.com/questions/17436364/grails-split-config-groovy-into-multiple-files.

Also I'm kind of curious, by what's meant, by "machine writable", as many plugins installs/quick start scripts, write to the config file. Although I'm sure the way they do it is not ideal. and Yaml must be easier to programmatically merge and update.

On Sunday, March 15, 2015 at 11:47:54 PM UTC-4, Henrique Lobo Weissmann wrote:
What about the DataSources.groovy file? Will it be removed too?

On Fri, Mar 13, 2015 at 12:33 AM, virtual dogbert <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="famyJDu0-KYJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">virtual...@...> wrote:
So I've noticed that Grails 3.0 uses Yaml for configuration, and I have several questions around it:

Why Yaml, just because it seem to be Spring Boots default?

Is there any gain, or advantage of yaml over Groovy based configuration?

Is this decision more of a time based thing? 

it seems with Pivotal's decision Grails 3.0 is a little rushed out the door, especially considering discussed time lines during springone 2gx. Is this something that maybe revisited?

I know that you can use Groovy in place of the yaml. Is there any down side?

Will there be a profile with Groovy configuration?

Thank you if  you have time to answer this. Over all Grails 3.0 looks like it's going to be another great leap forward, despite the fight I know I'm going to have upgrading to it.

--
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="famyJDu0-KYJ" 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="famyJDu0-KYJ" 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/1b4fa638-8a49-4a1f-baba-0ec72215ddd8%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href='https://groups.google.com/d/msgid/grails-dev-discuss/1b4fa638-8a49-4a1f-baba-0ec72215ddd8%40googlegroups.com?utm_medium\75email\46utm_source\75footer';return true;" onclick="this.href='https://groups.google.com/d/msgid/grails-dev-discuss/1b4fa638-8a49-4a1f-baba-0ec72215ddd8%40googlegroups.com?utm_medium\75email\46utm_source\75footer';return true;">https://groups.google.com/d/msgid/grails-dev-discuss/1b4fa638-8a49-4a1f-baba-0ec72215ddd8%40googlegroups.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.



--
Henrique Lobo Weissmann (Kico)
(55) 31 9226-0459
<a href="http://devkico.itexto.com.br" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Fdevkico.itexto.com.br\46sa\75D\46sntz\0751\46usg\75AFQjCNGIXnQdS1kxKcZxxhX8-7co7__Dkg';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Fdevkico.itexto.com.br\46sa\75D\46sntz\0751\46usg\75AFQjCNGIXnQdS1kxKcZxxhX8-7co7__Dkg';return true;">http://devkico.itexto.com.br
<a href="http://www.twitter.com/loboweissmann" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Fwww.twitter.com%2Floboweissmann\46sa\75D\46sntz\0751\46usg\75AFQjCNGwsNvUf0a5YjnnDIbJmXMVIjqWtA';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Fwww.twitter.com%2Floboweissmann\46sa\75D\46sntz\0751\46usg\75AFQjCNGwsNvUf0a5YjnnDIbJmXMVIjqWtA';return true;">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/51c78310-f0d9-483f-8d85-ebcd007eade1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Grails 3.0 and Yaml why? Is something gained by it or is it a time constraint reason?

vahid
I think something similar discussed a few threads back:

https://groups.google.com/forum/#!topic/grails-dev-discuss/_5VtFz4SpDY


On Monday, March 16, 2015 at 5:43:49 AM UTC, virtual dogbert wrote:
"The configuration of the application will need to be migrated, this can normally be done by simply renaming grails-app/conf/Config.groovy to grails-app/conf/application.groovy and merging the content of grails-app/conf/DataSource.groovy into grails-app/conf/application.groovy." from <a href="http://grails.github.io/grails-doc/3.0.x/guide/single.html#upgradingApps" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Fgrails.github.io%2Fgrails-doc%2F3.0.x%2Fguide%2Fsingle.html%23upgradingApps\46sa\75D\46sntz\0751\46usg\75AFQjCNFd8vpukqG7UeUr27cux-my91Z8zg';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Fgrails.github.io%2Fgrails-doc%2F3.0.x%2Fguide%2Fsingle.html%23upgradingApps\46sa\75D\46sntz\0751\46usg\75AFQjCNFd8vpukqG7UeUr27cux-my91Z8zg';return true;">http://grails.github.io/grails-doc/3.0.x/guide/single.html#upgradingApps

Which puts potentially a lot of configuration in one file, that doesn't nesesarily go together.  So hopefully there is a way to split up config files like before:
<a href="http://stackoverflow.com/questions/17436364/grails-split-config-groovy-into-multiple-files" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Fstackoverflow.com%2Fquestions%2F17436364%2Fgrails-split-config-groovy-into-multiple-files\46sa\75D\46sntz\0751\46usg\75AFQjCNHhaqTY_378WL3g_cdAXvIv7-m7Qg';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Fstackoverflow.com%2Fquestions%2F17436364%2Fgrails-split-config-groovy-into-multiple-files\46sa\75D\46sntz\0751\46usg\75AFQjCNHhaqTY_378WL3g_cdAXvIv7-m7Qg';return true;">http://stackoverflow.com/questions/17436364/grails-split-config-groovy-into-multiple-files.

Also I'm kind of curious, by what's meant, by "machine writable", as many plugins installs/quick start scripts, write to the config file. Although I'm sure the way they do it is not ideal. and Yaml must be easier to programmatically merge and update.

On Sunday, March 15, 2015 at 11:47:54 PM UTC-4, Henrique Lobo Weissmann wrote:
What about the DataSources.groovy file? Will it be removed too?

On Fri, Mar 13, 2015 at 12:33 AM, virtual dogbert <[hidden email]> wrote:
So I've noticed that Grails 3.0 uses Yaml for configuration, and I have several questions around it:

Why Yaml, just because it seem to be Spring Boots default?

Is there any gain, or advantage of yaml over Groovy based configuration?

Is this decision more of a time based thing? 

it seems with Pivotal's decision Grails 3.0 is a little rushed out the door, especially considering discussed time lines during springone 2gx. Is this something that maybe revisited?

I know that you can use Groovy in place of the yaml. Is there any down side?

Will there be a profile with Groovy configuration?

Thank you if  you have time to answer this. Over all Grails 3.0 looks like it's going to be another great leap forward, despite the fight I know I'm going to have upgrading to it.

--
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 grails-dev-discuss+[hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/grails-dev-discuss/1b4fa638-8a49-4a1f-baba-0ec72215ddd8%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href='https://groups.google.com/d/msgid/grails-dev-discuss/1b4fa638-8a49-4a1f-baba-0ec72215ddd8%40googlegroups.com?utm_medium\75email\46utm_source\75footer';return true;" onclick="this.href='https://groups.google.com/d/msgid/grails-dev-discuss/1b4fa638-8a49-4a1f-baba-0ec72215ddd8%40googlegroups.com?utm_medium\75email\46utm_source\75footer';return true;">https://groups.google.com/d/msgid/grails-dev-discuss/1b4fa638-8a49-4a1f-baba-0ec72215ddd8%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" 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.



--
Henrique Lobo Weissmann (Kico)
(55) 31 9226-0459
<a href="http://devkico.itexto.com.br" rel="nofollow" target="_blank" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Fdevkico.itexto.com.br\46sa\75D\46sntz\0751\46usg\75AFQjCNGIXnQdS1kxKcZxxhX8-7co7__Dkg';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Fdevkico.itexto.com.br\46sa\75D\46sntz\0751\46usg\75AFQjCNGIXnQdS1kxKcZxxhX8-7co7__Dkg';return true;">http://devkico.itexto.com.br
<a href="http://www.twitter.com/loboweissmann" rel="nofollow" target="_blank" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Fwww.twitter.com%2Floboweissmann\46sa\75D\46sntz\0751\46usg\75AFQjCNGwsNvUf0a5YjnnDIbJmXMVIjqWtA';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Fwww.twitter.com%2Floboweissmann\46sa\75D\46sntz\0751\46usg\75AFQjCNGwsNvUf0a5YjnnDIbJmXMVIjqWtA';return true;">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/dd51f7d4-ff39-4762-b398-1cc9e8b18ad2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.