[ROO-3633] Roo Shell won't start with 2.0.0.M1 Created: 13/Jun/15  Updated: 01/Jul/15  Resolved: 01/Jul/15

Status: Closed
Project: Spring Roo
Component/s: @ ROO SHELL
Affects Version/s: 2.0.0.M1
Fix Version/s: 2.0.0.M2

Type: Bug Priority: Minor
Reporter: Alejandro Matos Assignee: Juan Carlos García del Canto
Resolution: Duplicate Votes: 0
Labels: Roo, STS
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

MacOS X, STS 3.6.4.RELEASE, Roo 2.0.0.M1

Issue Links:
relates to ROO-3635 Spring Roo doesn't prevent version ch... Open


Preferences => Spring => Roo Support

If I change the installation to 2.0.0.M1 (downloaded, unzipped, copied to the same root where 1.3.1.RC1 is), the shell won't start giving the message: "Please stand by until the Roo Shell is completely loaded."
If I select 1.3.1 and restart the IDE, the shell starts properly.

Comment by Enrique Ruiz (DiSiD) [ 14/Jun/15 ]

You are right Alejandro, Roo Support for STS has needed some refactorings, unfortunately the new Roo Support will be available in STS 3.7.0 which is scheduled for end of June/early July. That version will be published to the Marketplace as well, means that the Roo support in the Marketplace will be updated then.

If you wanna test/install the updated Roo components before, you would need to do that manually via the Spring IDE nightly update site.

Comment by Enrique Ruiz (DiSiD) [ 30/Jun/15 ]

Alejandro, STS 3.7.0 has been published, feel free to install it and try Roo 2.0.0.M1.

Please let us know if all goes right

Comment by Alejandro Matos [ 30/Jun/15 ]

Is this and this a normal behaviour?
I lost all the generated classes after I started STS 3.7.0 with Roo 2.0.0.M1

Comment by Enrique Ruiz (DiSiD) [ 30/Jun/15 ]

Hi Alejandro, lamentably yes, it's the normal behaviour.

Spring Roo 2.0 has important changes to achieve the goals we defined at https://spring.io/blog/2015/03/30/looking-ahead-to-spring-roo-2-0 due to that it contains API changes and less add-ons than previous version so this release probably won't be backward compatible with 1.x. It means Spring Roo 2.0 cannot neither update nor modify applications created with Spring Roo 1.x

Comment by Alejandro Matos [ 30/Jun/15 ]

so it means I have to create the classes again? isn't there a way to prevent such action? or at least warn the developer before all this?

Comment by Juan Carlos García del Canto [ 01/Jul/15 ]

Hi Alejandro,

As you could see on ROO-3622, Spring Roo 2.0.0.M1 includes support to detect ROO version changes before apply changes on generated projects.

I've just tested again on system shell and it's working correctly:

I've tested on STS 3.7 and seems like is not applying this validation.. I've create an issue on this JIRA to solve it on future versions of STS Roo Support (ROO-3635)

Best regards and thanks for your contributions!

Comment by Juan Carlos García del Canto [ 01/Jul/15 ]

Created issue ROO-3635 to solve this error on STS 3.7+

Generated at Fri Aug 14 15:14:22 UTC 2020 using Jira 8.5.4#805004-sha1:0444eab799707f9ad7b248d69f858774aadfd250.