ext-all-debug.js 404 Not Found #4

Open
lyhcode opened this Issue Nov 11, 2011 · 6 comments

Comments

Projects
None yet
4 participants

lyhcode commented Nov 11, 2011

Test with Grails 2.0.0.M2.
I think the Resources Plugin cause files in 'ext' directory not accessible.

Owner

padcom commented Nov 12, 2011

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?

lyhcode commented Nov 13, 2011

ext/bootstrap.js => ok
ext/ext-all.js => ok
ext/ext-all-debug.js => 404 not found

If I don't use the extjs4 plugin and put a "ext" directory in web-app, I get a same result.
So I think the filename "ext-all**-debug**.js" can not be processed with the resources plugin.
If I turn of the resources plugin in BuildConfig.groovy with comment line below.

//compile ":resources:1.0.2"

It just works.
But the resources plugin have some useful features like compressing js and css files.
Maybe need to add some configuration to get resources plugin work with "ext-all-debug.js".
I keep trying...

Owner

padcom commented Nov 13, 2011

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.

Owner

padcom commented Jan 21, 2012

I've encountered a number of issues like this after moving to Grails 2.0.
It looks like the extjs and extjs4 plugins are not compatible with the
resources plugin.

If you want to use it at this point you'll have to uninstall the resources
plugin for now.

Matthias.

2012/1/21 Thomas Borg Salling <
reply@reply.github.com

Any news on this? Grails 2.0.0 and extjs4 4.0.7.0 still has the same issue.


Reply to this email directly or view it on GitHub:
#4 (comment)

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment