I am finishing reading a book that I only now realized was written for Grails 1.1.1! We are on version 1.3.7 which seems light years away in Programming language terms.
Could anyone give a distilled comparison between Grails versions? What new features should I be aware that were added after 1.1.1?
Each version ships with a set of Release Notes that outline the major changes. All of the major releases can be found on the Grails archive download page.
Reading through the latest documentation will probably help, too.
Related
I have an application which loads some external data based on gremlin.
I want to use it to load the data into a Neo4j database.
I saw that there was partial support for gremlin in previous versions but couldn't find any solution for latest version.
I'll be happy to hear if it is still possible and how can it be done.
At this point, TinkerPop expects to support 3.4.11 in its future 3.5.0 release (here) which is yet several months away. For TinkerPop to support 4.0 it would need a fresh release of the neo4j-tinkerpop-api-impl to be released with that version. It seems an issue has been created for that here.
I have several applications created with grails 1.2.2. I need to modify one of these applications to work with multiple datasources. It seems that my best option is to upgrade to a new version of grails. I'm worried that trying to go straight to grails 3 will cause major issues, but am not sure which versions to step through if I'm going to upgrade gradually. Any advice? I apologize for this being so open ended.
The first info about support for multiple databases in official docs exists in version 2.0.0:
http://docs.grails.org/2.0.0/guide/conf.html#multipleDatasources
Check out this guide for upgrade:
http://docs.grails.org/2.0.0/guide/gettingStarted.html#upgradingFromPreviousVersionsOfGrails
I made an example project in grails 2.3.8. How to upgrade to the newest version? No way to downgrade from version too?
It really depends on the differences between the versions. In a lot of cases you will get away with simply editing the version number in the application.properties file at the top of the project. There used to be a grails upgrade command which attempted to do some of the work for you but that approach proved to be problematic for a number of reasons so it was removed in Grails 2.4. The normal upgrade procedure now is to edit the version number, which can be done using the grails set-version command (which just updates application.properties, see http://grails.org/doc/latest/ref/Command%20Line/set-grails-version.html) and then reading release notes for any other particulars related to that release. Often the release notes suggest updating some specific plugins to specific version numbers for compatibility.
Downgrading generally could be done with the same approach. Depending on what is in your application you might run into problems going backwards in versions.
I hope that helps.
It seems like this questions should be easy but the installation requirements for Grails (http://www.grails.org/Installation) haven't been updated in 2 years. Does anyone know for sure is Grails 2.3 will run on JDK 8?
As noticed by heikkim this ticket which is now closed suggests that support for Java 8 will start on Grails 2.4:
http://jira.grails.org/browse/GRAILS-11063 (title: Java 8 support)
Tried an app (built on v2.3.7) on JDK 8 and hit a road block with database-migration plugin while compiling the app. If that particular plugin is commented out then everything looks good during compilation.
Running the app (with a sample controller) throws an error related to withFormat method from grails-plugin-mimetypes. Looking into it.
Raised an improvement defect for grails-database-migration plugin. I think this may not be required as well but making grails JDK8 compatible might need changes in grails-core. However, I have not checked with latest milestone build for Grails 2.4 which might already be taking care of those compatibility issues.
I am a few weeks from hopefully launching my site (Yes, I know like I may be tempting fate, even merely asking this question).
I am developing using SF 1.2.9 (using Propel ORM), but I am increasingly being tempted to upgrade to 1.4, least of all, I feel it will be less of an effort to migrate a life system from 1.4 to 2.0 later on, than from 1.2 to 1.4. Also, IIRC, active support for 1.2 is being phased out next year, whereas 1.4 is to be supported till 2012 (IIRC).
So, shall I bite the bullet and upgrade, or shall I take the (on the face of it - safer) option and stay put with 1.2.9?
If you want to use some of the new features, you should upgrade of course. As the symfony development is test driven, I assume the new versions are stable and reliable.
But: Do not upgrade to 1.4 but to version 1.3. The later has an extra compatibility layer to ensure that projects based on 1.2 still work. There are some internal changes in 1.4 that forces you to really refactor some parts of your project to keep it working. With 1.3 you can make this changes step by step.
The only differences between 1.3 and 1.4 is this compatibility layer. For specific instructions, read this upgrade guide.
As for support, 1.3 is supported until the end of next year which gives you plenty of time to upgrade to 1.4 step by step.
And in general I belief also that upgrading from 1.4 to 2.0 will be easier than from 1.2.
Edit:
You can find the changes here and the deprecated stuff here.
I don't know if 'internal changes' was the right word. There is some stuff you have to consider if you change to 1.4 but the deprecated stuff in 1.4 still works in 1.3.
I will try to upgrade one of my projects to 1.3 this weekend and I can give you feedback somehow if you want to.
Are their any compelling reasons for the upgrade? Does version 1.4 have more bug fixes, or additonal features that your appliation must have? Are their any breaking changes between 1.2.9 and 1.4? Is there any refactoring to do after you've upgraded to 1.4 from 1.2.9?
I'm looking at this from a .net framework perspective;
.net 1.1 to 2.0 - there were many changes here. many of them were breaking changes, but the benefits of the upgrade were great.
.net 2.0 to 3.0 or 3.5 - a lot of upgrades were introduced here, but not very many if any breaking changes since the last two upgrades were based on the same basic framework. You can live with the 2.0 version without upgrading to any of the other two.
So if the Symfony upgrade is similiar, I would wait for a little while. You've got your application built, tested and ready to go. See what it takes for the upgrade and then see about integrating the new features in during the next iteration of your development.
Good luck with your site, and hope this helps some.