New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discontinue Grails 2.x plugin #456

Closed
erdi opened this Issue Oct 8, 2016 · 4 comments

Comments

Projects
None yet
2 participants
@erdi
Member

erdi commented Oct 8, 2016

With Grails 3.0 released in March 2015 and the Grails team urging everybody to upgrade there seems to be little point in releasing new version of the Grails 2.x plugin for Geb. It will be still possible to use newer versions of Geb with Grails 2.x by it will have to by done by specifying which version of Geb is supposed to be used in BuildConfig.groovy file of the Grails 2.x project.

Projects using Grails 3.x can use the built-in support for Geb, see https://github.com/grails3-plugins/geb and http://docs.grails.org/3.1.6/guide/testing.html#functionalTesting.

@erdi erdi changed the title from Remove Grails 2.x plugin to Discontinue Grails 2.x plugin Oct 8, 2016

@aadrian

This comment has been minimized.

Show comment
Hide comment
@aadrian

aadrian Oct 8, 2016

On the contrary - it's only wish thinking from the Grails Team side. Many projects won't be migrated Grails 3 since it's not backward compatible with 2 and there's also not automated migration. Not everybody gets budget all the time to rewrite stuff.

aadrian commented Oct 8, 2016

On the contrary - it's only wish thinking from the Grails Team side. Many projects won't be migrated Grails 3 since it's not backward compatible with 2 and there's also not automated migration. Not everybody gets budget all the time to rewrite stuff.

@erdi

This comment has been minimized.

Show comment
Hide comment
@erdi

erdi Oct 9, 2016

Member

As I said, it will still be possible to use newer Geb versions together with Grails 2.x. It's just that you won't be upgrading the version of the plugin but you will have to modify the dependencies in BuildConfig.groovy of your Grails application while using the 1.0 version of the plugin.

You should not expect that OSS projects will support your outdated dependencies because you "don't get the budget" to keep your whole stack up to date. If you freeze part of your stack to a certain version then be prepared that you will have to freeze other bits of it too.

Member

erdi commented Oct 9, 2016

As I said, it will still be possible to use newer Geb versions together with Grails 2.x. It's just that you won't be upgrading the version of the plugin but you will have to modify the dependencies in BuildConfig.groovy of your Grails application while using the 1.0 version of the plugin.

You should not expect that OSS projects will support your outdated dependencies because you "don't get the budget" to keep your whole stack up to date. If you freeze part of your stack to a certain version then be prepared that you will have to freeze other bits of it too.

@aadrian

This comment has been minimized.

Show comment
Hide comment
@aadrian

aadrian Oct 9, 2016

because you "don't get the budget" to keep your whole stack up to date.

It's not just me, but almost all projects I've seen are in this situation, since management usually does not accept "budget for upgrade just for the sake of it, because new versions are incompatible".

There was zero reason for Grails 3 to be that incompatible (and require complete rewrite of apps) with 2.
This way they also made all the Grails books and courses obsolete.

aadrian commented Oct 9, 2016

because you "don't get the budget" to keep your whole stack up to date.

It's not just me, but almost all projects I've seen are in this situation, since management usually does not accept "budget for upgrade just for the sake of it, because new versions are incompatible".

There was zero reason for Grails 3 to be that incompatible (and require complete rewrite of apps) with 2.
This way they also made all the Grails books and courses obsolete.

@erdi

This comment has been minimized.

Show comment
Hide comment
@erdi

erdi Oct 9, 2016

Member

Sorry, but this tracker is not a relevant place for your sentiments about Grails.

Member

erdi commented Oct 9, 2016

Sorry, but this tracker is not a relevant place for your sentiments about Grails.

@erdi erdi self-assigned this Nov 29, 2016

@erdi erdi added this to the 1.1 milestone Nov 29, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment