Grails

"taglib" direcive in GSP no longer works

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.1-beta1
  • Fix Version/s: 1.1-beta2
  • Component/s: View technologies
  • Labels:
    None
  • Environment:
    Debian Linux, OpenJDK 6, Grails 1.1-SNAPSHOT (r7232)

Description

I had the following directive in my GSPs, following the instruction at http://grails.org/Eclipse+IDE+Integration :

<%@ taglib prefix="g" uri="/web-app/WEB-INF/tld/grails.tld" %>

This worked in 1.0.3, but no longer works in 1.1-SNAPSHOT. The GSP tags are now completely ignored. To fix it I just removed the directive (breaking code completion in Eclipse).

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Graeme Rocher added a comment -

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

Show
Graeme Rocher added a comment - 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
Hide
Permalink
Marcus Better added a comment -

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

Show
Marcus Better added a comment - That's fine. I added a note to the wiki page.
Hide
Permalink
Jean-Noël Rivasseau added a comment -

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...

Show
Jean-Noël Rivasseau added a comment - 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...
Hide
Permalink
Jean-Noël Rivasseau added a comment -

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.

Show
Jean-Noël Rivasseau added a comment - 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.
Hide
Permalink
Graeme Rocher added a comment -

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

Show
Graeme Rocher added a comment - 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
Hide
Permalink
Graeme Rocher added a comment -

Reduced priority of non critical issues which have current workarounds

Show
Graeme Rocher added a comment - Reduced priority of non critical issues which have current workarounds
Hide
Permalink
Jean-Noël Rivasseau added a comment -

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,

Show
Jean-Noël Rivasseau added a comment - 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,
Hide
Permalink
Graeme Rocher added a comment -

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

Show
Graeme Rocher added a comment - Ok an error is now printed if you try and override the default namespace

People

Vote (5)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.1#660-r161644) | Report a problem
Powered by a free Atlassian JIRA open source license for Grails project. Try JIRA - bug tracking software for your team.