Difference between Spring Roo and JHipster
jhipster, spring-roo
Solution
I recommend you analize the requirements of your project and choose the right tool.
- JHipster is a good devel tool to create Spring Boot projects of AngularJS single-page web applications.
- Spring Roo 2 is a good devel tool to create, maintain and evolve Spring Boot projects of SpringMVC-Thymeleaf multi-page web applications. Take a look to the application architecture created by Roo 2.
You choose which is the right pattern for your project: single-page vs multi-page.
Note that by evolve a project I meant the tool can update the generated code without loosing your changes. Nowadays, JHipster cannot update the generated code without loosing your changes as said in its documentation (https://jhipster.github.io/creating-an-entity/#updating-an-existing-entity):
When you run the entity sub-generator for an existing entity, you will be asked a question ‘Do you want to update the entity? This will replace the existing files for this entity, all your custom code will be overwritten’ ...
Spring Roo is able to update and evolve the application code without loosing the developer changes. So, I recommend you review and check the features, patterns and good practices that each tool includes in your application and choose the one you think is better for your project.
Problem
I've been running some experiments with my own with Spring Roo and it seems to be pretty cool, but i heard that JHipster is better. What's different between Spring Roo and JHipster?