我从 Grails 2.2.1 升级到 2.2.2，但是现在运行时，找不到 spring security core 插件的默认属性。您可以从此屏幕截图中看到未找到属性。
有想法该怎么解决这个吗？
按照 Burt 的建议，我升级到了 grails 的 2.2.3 版本。但是，现在我得到以下信息：
Configuring Spring Security Core ...
... finished configuring Spring Security Core
| Server running. Browse to http://localhost:8080/movies
| Error 2013-06-25 06:06:11,580 [http-bio-8080-exec-6] ERROR [/movies].[gsp] - Servlet.service() for servlet [gsp] in context with path [/movies] threw exception
Message: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.
Line | Method
->> 1145 | runWorker in java.util.concurrent.ThreadPoolExecutor
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
| 615 | run in java.util.concurrent.ThreadPoolExecutor$Worker
^ 722 | run . . . in java.lang.Thread
| Error 2013-06-25 06:06:12,885 [http-bio-8080-exec-2] ERROR [/movies].[default] - Servlet.service() for servlet [default] in context with path [/movies] threw exception
Message: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.
Line | Method
->> 1145 | runWorker in java.util.concurrent.ThreadPoolExecutor
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
| 615 | run in java.util.concurrent.ThreadPoolExecutor$Worker
^ 722 | run . . . in java.lang.Thread
Disconnected from the target VM, address: '127.0.0.1:64820', transport: 'socket'
Process finished with exit code 255