Results 1 to 4 of 4

Thread: Red exclamation mark next to project name in project explorer

  1. #1
    Join Date
    Mar 2013
    Posts
    2

    Default Red exclamation mark next to project name in project explorer

    In the Groovy/Grails Tool Suite, when one creates a Grails 2.2 project, one have to manually change the Groovy compiler version to 2.0 (error: grails_tool_suite_error.jpg). After doing this, there's a red exclamation mark next to the project name in the project explorer window. What does the red exclamation mark mean? How can I get rid of the error? Re-compiling doesn't make it go away even though there seem to be no errors.
    Last edited by earthling; Mar 10th, 2013 at 04:41 PM. Reason: Attached a screenshot of the error before changing the Groovy compiler version

  2. #2
    Join Date
    Aug 2008
    Location
    Vancouver, BC
    Posts
    747

    Default

    Groovy-Eclipse only supports one groovy compiler at a time (ie- if you want to switch compiler levels, you must go into your preferences, switch and restart). Each Groovy project keeps track of the compiler level that it expects (currently, this is not being matched to the grails version that it expects, but it should).

    So, what is happening here is that since you originally created your project with a 1.8.6 level, your project expects a groovy 1.8.x compiler, but it is finding a 2.0.x compiler.

    To fix, select the project, right-click -> Groovy -> Fix Compiler Mismatch problems. This brings up a dialog that allows you to set the project compiler level to the workspace level. And this should remove the !.
    Andrew Eisenberg, Ph.D.
    SpringSource, a division of VMware
    SpringSource Tools Team
    More about AJDT, Groovy-Eclipse, and Grails tooling

  3. #3
    Join Date
    Mar 2013
    Posts
    2

    Default

    Thank you for your response, Andrew. I couldn't find the option "Fix Compiler Mismatch problems" initially. After looking around for a bit, this seemed to work: go to the Dashboard -> Extensions -> Select Groovy 2.0 -> Install -> Restart. This made the red exclamation mark disappear and the option "Fix Compiler Mismatch problems" to appear in the project, right-click -> Groovy menu. I'm not sure how I could switch to Groovy 2.0 initially if the plugin wasn't installed. I'd done a Project -> right click -> Properties -> Groovy Compiler -> Select 2.0 from the dropdown.
    Thanks a lot for the help! I had been struggling with this for a while!

  4. #4
    Join Date
    Aug 2008
    Location
    Vancouver, BC
    Posts
    747

    Default

    Apologies, I had been a bit misleading. Groovy 2.0 was not installed by default until the 3.2.0 release (officially announced today). Now Groovy 2.0 is installed in GGTS when you unzip it.
    Andrew Eisenberg, Ph.D.
    SpringSource, a division of VMware
    SpringSource Tools Team
    More about AJDT, Groovy-Eclipse, and Grails tooling

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •