What other areas of a v1.3.9 application should I focus on (as in update/upgrade in version or convention) to eliminate possible problems that would manifest running it as v2.5.6.Īny feedback whatsoever would be appreciated, as I'm a little stuck now after scouring the Grails docs for possible conflicts. I've upped the -Xmx to 1G just to try accommodate that, but to no avail. Just a fun way to change up your taskbar for something old but new. You get to replace your modern Windows taskbar with the classic Windows 95, 98, Me, 2000, or XP style. For monitoring performance, the app had grails-melody 1.21 plugin installed.
Open a new terminal or type the command: Then install the latest stable Grails version: If prompted, make this your. Simply open a new terminal and enter: Follow the on-screen instructions to complete installation. Startup doesn't actually complete as it throws an OutOfMemoryError on heap space RetroBar is a nostalgia-inducing little portable app that takes you back in time with classic Windows taskbars. We are maintaining a webapp developed in Grails 1.3.9. This tool makes installing the Grails framework on any Unix based platform (Mac OSX, Linux, Cygwin, Solaris, or FreeBSD) easy. Startup of the application is extremely slowĢ.
So far, this has gotten me past a wide range of initial errors encountered.
modified some Service's to use to fix a circular dependency updated oovy according to a sample 2.5.6. updated files installed by 'install-templates' modified controllers and services to accommodate new requirements (like changing methods to private/protected where necessary) updated all dependency libraries and plugins to be Grails 2.x compatible. It's been something we've not had the time to devote to until now, but can no longer afford not to. So I'm upgrading the web application component of our company product from Grails 1.3.9 to Grails 2.5.6.