Upgrading to 1.6.0-GA

[jearles]

Hi,

I see that 1.6.0-GA has been formally released! YEAH!!!

We originally started building our application based on 1.5.0-GA and have been upgrading along as the patch releases came out. Is there an existing list of any schema changes that we should make sure are applied before we upgrade to 1.6.0-GA? If not, I guess I'll generate a new project based on the Maven archetype and get it to generate a new schema so I can do a diff.

Thanks for all your continual efforts!

- John

[bpolster]

John,

We are working on some upgrade documentation this week. Keep on the lookout for a message (via Twitter) or here in the forum once we have the upgrade information complete.

1.5 to 1.6 is a fairly major change but one that we highly recommend everyone try to do. We have reorganized some of the project modules in order to better support external additions to the framework.

[jearles]

Thanks Brian.

After a 2-day effort I finally have finished our upgrade effort. It wasn't that difficult, but the package refactoring made XML reconfiguration a bit of trial and error redeployment exercise. One issue that I believe we were left with was a reference to an asset.server.url.prefix.secure property that couldn't be resolved for blStaticAssetService. I had to add an empty placeholder into our default config properties file.

[bpolster]

Wow, nice job.

We didn't think anyone would be able to accomplish that without a migration guide. The pain will be worth it as it will allow for better velocity in the future.