Menu
The documentation created by running grails doc is not completely satisfactory in my eyes. For example, actions in controllers appear as properties in the documentation, though I would wish to have an extra section to separate actions from actual properties (Strings etc.).
Are there any tools that operate on JavaDoc-like comments and generate better output for Grails projects? It should be either Grails-aware (i.e. understands that closures in controllers are actually actions) or allow explicit tagging (e.g. a @section Actions comment makes the paragraph appear in a section called "Actions")
454
When assessing the two solutions, reviewers found Grails easier to use, set up, and do business with overall. However, reviewers preferred the ease of administration with Spring Framework. Reviewers felt that Spring Framework meets the needs of their business better than Grails.
Overall, Grails is much more rough-around-the-edges than Rails is, partially due to its immaturity, and partially because it relies on two insanely complex frameworks under-the-covers (Spring and Hibernate). Rails also has a much bigger community.
The Grails framework is built on top of Spring Boot and leverages Spring Boot's time-saving features, such as Spring-powered dependency injection.
Grails is a Java-based web application framework that uses the Apache Groovy programming language.
Take a look at the grails-new-doc project.
194
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
