Check out "Grails Runtime Docs" plugin ( http://grails.org/plugin/grails-runtime-docs ). It will generate groovy documentation from runtime including the dynamic methods, adding "Dynamic Method Summary" & "Dynamic Method Detail" in the generated html docs which provide their source information. It's more Grails aware and categorizes the classes into Controllers, Commands, Domains, Services and Tag Libraries. Note: I'm a grails developer and contributed this open-source plugin to Grails myself. Hope you find it useful.
It sounds like you are running an older version of Grails.
The latest version of Grails contains many improvements in grails doc. In addition, Grails now recommends controller actions should be coded as methods rather than closures, which may address your issue.
If you are concerned about upgrading, I've been using Grails since 2008 and always upgrade when new versions come out.
It has never taken more than one day to upgrade Grails, update code to address any documented "breaking changes", run the tests, and revert if I find any issues.
Since upgrading is so easy, I always try to keep up with the latest stable release.
By the way plugins can be problematic. You should, or course, have tests for any plugins you use. In fact the better plugins already include tests, which you can run.
发布评论
评论（3）
查看 grails-new-doc 项目。
Take a look at the grails-new-doc project.
查看“Grails 运行时文档”插件 ( http://grails.org/plugin/grails-runtime-文档）。它将从运行时生成常规文档，包括动态方法，添加“动态方法摘要”和“动态方法摘要”。生成的 html 文档中的“动态方法详细信息”提供了其源信息。它更具有 Grails 意识，并将类分类为控制器、命令、域、服务和标签库。
注意：我是一名 Grails 开发人员，我自己向 Grails 贡献了这个开源插件。希望您觉得它有用。
Check out "Grails Runtime Docs" plugin ( http://grails.org/plugin/grails-runtime-docs ). It will generate groovy documentation from runtime including the dynamic methods, adding "Dynamic Method Summary" & "Dynamic Method Detail" in the generated html docs which provide their source information. It's more Grails aware and categorizes the classes into Controllers, Commands, Domains, Services and Tag Libraries.
Note: I'm a grails developer and contributed this open-source plugin to Grails myself. Hope you find it useful.
听起来您正在运行旧版本的 Grails。
最新版本的 Grails 包含 grails 文档中的许多改进。此外，Grails 现在建议控制器操作应编码为方法而不是闭包，这可能会解决您的问题。
如果您担心升级，我自 2008 年以来一直在使用 Grails，并且总是在新版本出现时进行升级。
升级 Grails、更新代码以解决任何记录在案的“重大更改”、运行测试以及在发现任何问题时进行恢复从未花费超过一天的时间。
由于升级非常容易，因此我总是尝试跟上最新的稳定版本。
顺便说一句，插件可能会出现问题。当然，您应该对您使用的任何插件进行测试。事实上，更好的插件已经包含可以运行的测试。
It sounds like you are running an older version of Grails.
The latest version of Grails contains many improvements in grails doc. In addition, Grails now recommends controller actions should be coded as methods rather than closures, which may address your issue.
If you are concerned about upgrading, I've been using Grails since 2008 and always upgrade when new versions come out.
It has never taken more than one day to upgrade Grails, update code to address any documented "breaking changes", run the tests, and revert if I find any issues.
Since upgrading is so easy, I always try to keep up with the latest stable release.
By the way plugins can be problematic. You should, or course, have tests for any plugins you use. In fact the better plugins already include tests, which you can run.