-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ext-all-debug.js 404 Not Found #4
Comments
Well, that shouldn't have any influence unless Grails 2.0 will not serve static content at all. Did you have any luck getting it to work with 2.0? |
ext/bootstrap.js => ok If I don't use the extjs4 plugin and put a "ext" directory in web-app, I get a same result.
It just works. |
Let me know how it turns out. If you find out how to overcome the problem please make a pull request so that others can benefit from your findings. Thanks! |
Any news on this? Grails 2.0.0 and extjs4 4.0.7.0 still has the same issue. |
I've encountered a number of issues like this after moving to Grails 2.0. If you want to use it at this point you'll have to uninstall the resources Matthias. 2012/1/21 Thomas Borg Salling <
|
The extjs4 plugin is compatible with Grails 2.0. I explicitly tested it with Grails 2.1.1, but I presume it should work with any Grails 2.x version. The key is that there's no good reason I can see to use bootstrap.js to load your ext files. If you wish to load the -debug version in development environments only then you can put condition logic in your layout gsp to load different resource bundles, one that has the -debug ext file, and one that does not. And the resources plugin will then load these files just fine. While it may be possible, this conditional environment logic does not really belong in your *Resources.groovy file. |
Test with Grails 2.0.0.M2.
I think the Resources Plugin cause files in 'ext' directory not accessible.
The text was updated successfully, but these errors were encountered: