TFA might be right about Rails but completely wrong about Spring. Spring is absolutely a web framework--templates and all. With Spring Boot and modern Java, the productivity is probably in same ballpark too.
You are still missing Turbolinks, the rails console, JPA is nowhere as good as Active Record, rails scaffolding, Rspec, Devise, then you need to setup migrations... I could add a lot of other items, but no it's nowhere near rails yet. I've never found anything approaching rails for the speed of coding (but not the speed of execution unfortunately :/).
Rails templates is a very very small part of what makes it so quick to write code.
I think I agree about migrations. Flyway is useful but not as clean or easy as ActiveRecord and I think that depends on Ruby's dynamic nature so it would be hard to replicate.
You surely meant to write that the other way round.
Edit: JPA is usable yes, most ORM nowadays are quite good anyway, it's just that Active Record is still always one step above, it's a pleasure to work with.
This means you have to go away and do some research to get your stack running.
This was enough to put me off.
persistance: spring-data, the JPA/Hibernate based library for SQL access appears to be very opinionated and is very simple to fully understand. I have never used MongoDB, but spring-data-mongodb is probably of equal quality.
DB migrations: What do you mean?
Support for Groovy Templates is legacy and not as equal as the other choices. Groovy is now Apache Groovy, and on the decline.
You can use the DI and config management container spring-core by itself. There are actually THREE web-frameworks: spring-webflux, spring-web and spring-web-mvc. Webflux is the new framework for "reactive HTTP", spring-web contains the conventional web/REST-server capabilities and spring-web-mvc offers mvc functionality with templates and depends on spring-web.
Correct me if I am wrong.