Spring Roo Reviews in May 2025: User Ratings, Pros & Cons

Spring roo for fast development cycle

What do you like best? Easy built-up of crud functions. Dependency removal is easy. What do you dislike? It has not evolved since long. Making your own changes is difficult. Recommendations to others considering the product: Are you planning to have significant customisation; in that cae evaluate Spring roo thoroughly. What problems are you solving with the product? What benefits have you realized? Building crud functions in matter of minutes. Basic integrity with data sources.

Spring Roo helped me with creating and scaffolding projects.

What do you like best? Scaffolding is dynamic, customizable, repeatable. Most of the code is moved to aspects. What do you dislike? Project seems to be dead for long time. Ngnix seems to follow. Recommendations to others considering the product: Create your own annotations to create customizable scaffolding. What problems are you solving with the product? What benefits have you realized? Whole database layer is just matter of create Entities and everything is generated ...

When I tried Spring Roo it was too cumbersome to use with too little features.

What do you like best? command line interface for generating code. What do you dislike? It seems that jHipster is WAAAAY more powerful with more combinations and frameworks than Spring Roo. Frontend is old way of doing web. Spring Roo is still using MVC pattern. While in jHipster you can use Angular, React,Vue. You can setup as microservices. Missing NoSQL support, Kafka integration. Recommendations to others considering the product: use jHipster :) What problems are you ...

Great tool for getting started

What do you like best? Low learning curve, ease of front end and backend integration. Less dependencies than Spring Boot What do you dislike? Limited library for creating sophisticated user interfaces. Recommendations to others considering the product: Consider the required UI sophistication required by application before going to spring roo What problems are you solving with the product? What benefits have you realized? Simple 3-tier applications

Great for Full Stack developer

What do you like best? It's very easy to use we can generate ready made production code . Helpful for CRUD like application. What do you dislike? We need to modify or delete the code after generation of code in frontend as well as backend which sometimes takes more time. Recommendations to others considering the product: Good for ready made frontend and backend code.I mostly used as a CRUD application and easy to use if you know Spring Framework and basic UI like html,css, ...

Used roo long time ago, could not install it on mac

What do you like best? roo console, flexibility, creation of apps based on standard application architecture. There is huge potential with spring roo, I would prefer it, in comparing with jhipster for example. But some bad things should be solved. What do you dislike? could not install new version on sts4, on my mac, there is no intelij plugin. For library like this, simple installation process should be mandatory. Recommendations to others considering the product: learning ...

Easy to use

What do you like best? Can up and run the application with less Effort What do you dislike? Things have been auto-configured and later hard to identify. Auto-generated code is very complex some times a bit hard to apply changes manually. What problems are you solving with the product? What benefits have you realized? I have used Spring Roo to complete one of my industry projects. The beauty of Spring Roo is it helps to generate and up and run complete Spring Web application with ...

RAD with JAVA - Spring Roo

What do you like best? Faster development than before. It’s scaffolding technique is very helpful to create the CRUD functionalities from DB design. What do you dislike? UI development is still manual. The default UI is not attractive and customisation of UI is complicated. What problems are you solving with the product? What benefits have you realized? Faster development.

Worked explicity with ROO to create boiler plate code, configure projects

What do you like best? Had the first encounter with Roo, couple of years back, wherein we kickstarted the project with simple spring roo shell and configured packages maven-arch type web project JPA provider. Model definition MVC Thymleaf templates for models It was a bliss. What do you dislike? Nothing in particular. But off late, we have much wide IDE support, spring boot https://start.spring.io/ which kind of makes roo redundant. Recommendations to ...

Have used spring Roo to do Rapid application development and generated the UI for CRUD operations

What do you like best? Using spring Roo, we can do Rapid application development What do you dislike? I haven't encounter such things, which i don't like in this technologies. Recommendations to others considering the product: Its great technology for rapid application development. What problems are you solving with the product? What benefits have you realized? Have generated user interface to do CRUD operation.