Jul 15th, 2009, 07:16 PM
STS 2.1.0 Roo Shell dead in Eclipse 3.5
I installed STS 2.1.0 on Eclipse 3.5 on Mac os 10.5.x Leopard as the per instructions at http://blog.springsource.com/2009/06...to-eclipse-35/.
When I opened the Roo shell view from Window->Show View. A window does open for Roo shell. However, I don't get any prompt to execute roo commands. The situation does not change even if I set an externally deployed Roo.
Am I missing anything? or is Eclipse Roo Shel view is broken?
Jul 16th, 2009, 01:25 AM
Interesting, I have not tried to install STS in a Eclipse 3.5 manually as described in Christians blog post since he actually released a bundled version just a few days after. So if you could try to download the current STS 2.1.0.RC1 release, that would probably solve the problem. At least it works for me .
Jul 16th, 2009, 04:13 PM
I have faced the same "issue" with STS 2.1 RC1 downloaded from the Update Site, but then I have realized that it's not the problem with STS.
To start a Roo Shell you need to right click on the project configured as Roo project and choose "Spring Tools" -> "Roo Shell". This works for me.
Jul 17th, 2009, 08:38 AM
I have it working too via Christian's blog post instructions. As piter75 mentioned, you have to launch the roo shell from your project structure.
This does raise a question. What happens if you have two roo shells open for the same project, one in Eclipse and another command line?
Jul 23rd, 2009, 03:29 PM
Roo helps create a new project structure. So, requiring a project structure to be present to launch Roo in eclipse is not very useful.
Basically, if you want to use Roo in Eclipse then:
Roo in STS requires you to use Roo on the command line, create a project structure, and then use Eclipse to launch Roo shell. Shouldn't this be a bug?
Would love to here SpringSource's view on this.
Jul 23rd, 2009, 06:12 PM
I think there is a misunderstanding here . Eclipse DOES help you to create a Roo project structure via File > New > Spring Template Project > Roo Simple (based Roo 1.0.0.M2). This creates a Roo M2 compliant project structure.
Now, since the release of STS 2.1.0 RC1 we have released a new version of Roo (RC1) which integrates some minor changes to the project structure. So until the next release of the STS 2.1.0 series is made available you have this minor problem that if you create a new Roo M2 project with STS you can not configure to use Roo RC1 against that because of the different project structure assumptions.
This leaves you with two choices:
1. Use STS to create a Roo M2 project and use the integrated Roo M2 shell to work with it.
2. Use Roo RC1 shell to create a project, create eclipse artifacts (mvn eclipse:eclipse) and import into STS 2.1 RC1, then change the integrated Roo version in STS to Roo RC1 and work with your project.
The next release of STS 2.1 will contain a new project template which is compliant with Roo RC1 and you have all other combinations available to you.
So in summary, there is no Roo or STS bug but rather they are currently not 100% in sync due to different release schedules.
Hope this clears things up.