Pain in upgrading from Roo+GWT 1.1.0 to 1.1.1 people

amy

This is more of a question towards the Roo+GWT team, is there proper steps that people should be taking to upgrade from 1.1.0 to 1.1.1?

I understand its not easy as upping the gwt and roo version in the pom file, there are dependences involved. So I created a skeleton project with the same name, top package, persistence amp; jdbc as a base to work from and slowing mirror the changes from the new pom.xml to my old pom.xml.

However, the process is not going smooth at all. After reconciled the pom.xml and started the roo shell, it tried to re-generate some roo files but immediately undo it automatically. Looks like it thinks the old Roo generated file has been somehow quot;modifiedquot; - which is not possible as the old Roo overwrite it if that happens. So I ended up manually cleaning up the quot;managedquot; directory so it can regen without problem.

Then comes the dreaded gae user thingy that everyone encounter (showthread.php?t=100960). Removing the gae directories helps but then the client/scaffold directory is out of wack. Seems  GWT's Roo plugin is not properly maintaining that directory and regen the files there with the newer version. So I had to manually clear them and copy them from the skeleton project.

Long story short, I further went thru reconciling the web.xml, the starting html page, comparing the webapp directory to see if I miss anything etc etc..

I goto a point where all the code compiles but still I am unable bring up either the applicationScaffold module nor my customized module. It just say failed to load the scaffold module.

So my question is, is there a plan from the Roo-GWT team to create a procedure to help people upgrading from version to version? I mean from 1.1.0 to 1.1.1 is suppose to be a minor upgrade but it pretty much breaks the whole thing if using GWT. My test project is not huge by any mean, however this would be a real concern for long term production use.

Anybody out there have this problem and have a solution? I will probably try to create another project by reapplying the log.roo then manually migrate my mods to the skeleton project just to see if I could get things working again.

Joseph

I have also had trouble upgrading from 1.1.0 to 1.1.1.  After upgrading STS to 2.5.2, Roo was having trouble generating projects- even if there was only 1 class with two data members.  Deleting the GAE folders in the project didn't help me any.  

I tried reinstalling STS from a freshly downloaded .zip with no luck.  

My fix was to install STS on my laptop and, outside a strange data nucleus enhancer warning, everything seems to be working fine.  My desktop is hosed though.  

Maybe I will try and get more specifics about the problems with my desktop STS/roo install, if it can help fix some bugs.