Grails 1.1 now supports custom JSP tag libraries and by doing the above you are overriding Grails built in tags, there is nothing we can do about this really. There needs to be an improved GSP editor for Ecilpse

That's fine. I added a note to the wiki page.

Closed as WONTFIX ??! This is IMHO an extremely important bug. The Eclipse integration / support for Grails is already at a near zero level. Dropping support for syntax coloring, completion and validation of GSP files is going to be really problematic. Isn't there a workaround or something that can be done? If not, I guess there should be some kind of announcement that using Grails with Eclipse is almost impossible at the moment...

When I mentioned a workaround: maybe it's possible to disable the JSP custom tag libraries support in Grails in exchange for this support? As I dont use JSPs at all I would happily just do that.

I agree with Graeme though that the real thing that needs to be done is a full-blown GSP editor for Eclipse.

On second thought, maybe we can add code to make it impossible to override the default namespace 'g' in which case we would printer a warning to the console. Users of the Eclipse plugin will for the meantime have to take this as a trade-off

Reduced priority of non critical issues which have current workarounds

I think the remark by Graeme (make it impossible to override the default namespace 'g' ) must absolutely make it into 1.1 - if it does not that would be a blocker for not using 1.1 for me, as I do need the Eclipse support for writing GSPs,

Ok an error is now printed if you try and override the default namespace