IntelliJ IDEA 15 EAP Supports Grails 3

If you are a Grails developer, you’ll be happy to know that IntelliJ IDEA 15 EAP brings the long-awaited support for Grails 3.  Now you can enjoy both: the latest features of your favorite web framework, and the coding assistance of your favorite IDE:

v15_grails

Coding assistance also includes navigation between your injected dependencies:

v15_grails_cdi

Note: to enable this feature in the latest EAP build, you have to manually define the conf/spring/resources.xml file. In the next EAP build, this will work out of the box.

Since Grails 3 is built on Spring Boot, to run or debug your Grails application, you can simply run/debug your main method:

v15_grails_run_debug

The old Grails run configuration accepting the Grails command line (e.g. run-app) is still there if you need it.

Since Grails 3 uses a new Gradle-based build system, Grails support fully leverages the IntelliJ IDEA Gradle integration: project dependencies are resolved automatically, you can run Gradle tasks, and rely on coding assistance when editing build files:

v15_grails_gradle

The current support also has its limitations:

  • The IDE doesn’t provide Grails Shell
  • Creating a new Grails 3 project is done via a separate item in the Project Wizard (and you still have to specify the path to your Grails SDK).
  • We drop the Grails tool window. We’re sorry about it, but for now we’ve decided to focus more on the in-editor coding assistance. Still we plan to come up with a view that is unified for all MVC frameworks in the future.

Download the latest IntelliJ IDEA 15 EAP build, give it a try, and share your feedback with us by writing to our discussion forum or submitting bug reports to the issue tracker.

Develop with Pleasure!

 

About Andrey Cheptsov

Part-time dreamer. JVM/JavaScript geek. IntelliJIDEA Marketing Manager at JetBrains.
This entry was posted in EAP Releases, New Features and tagged , , . Bookmark the permalink.

13 Responses to IntelliJ IDEA 15 EAP Supports Grails 3

  1. Phill Nacelli says:

    “We drop the Grails tool window. We’re sorry about it, but for now we’ve decided to focus more on the in-editor coding assistance. Still we plan to come up with a view that is unified for all MVC frameworks in the future.”

    Thanks for the update, bummed about the Grails Tool Windows though but looks like something else may be in its place.

    Where can we track progress on the feature mentioned above? Any plans when this would be available?

    Thanks,

  2. Seb says:

    Hi,

    when you write :

    “Note: to enable this feature in the latest EAP build, you have to manually define the conf/spring/resources.xml file.”

    what do you mean exactly ?

    thanks

    • Andrey Cheptsov says:

      I mean that in the latest EAP build the navigation to injected classes doesn’t work until you manually define a “conf/spring/resources.xml” file with an empty spring configuration.

  3. Ejaz Ahmed says:

    “We drop the Grails tool window. We’re sorry about it, but for now we’ve decided to focus more on the in-editor coding assistance. Still we plan to come up with a view that is unified for all MVC frameworks in the future.”

    You could have asked for community feedback before doing so. For the time being, lets hope there would be some better alternative.

  4. Ejaz Ahmed says:

    Unable to auto complete projects created using grails CLI. It is impossible to use current grails3 support with existing projects. It only works for projects created using Intellij. Moreover, there is no way to set profile of grails project while creating from IDE. Please correct me if I am wrong.

    • Ejaz Ahmed says:

      The issues posted above are related in grails 3.1.M1 which is in milestone release only. Intellij works fine for grails 3.0.8 and earlier releases.

  5. Pingback: Diario Grails (settimana 41 del 2015) | BME

  6. nisabek says:

    Hi,

    Is the UNIX version also supporting this? can’t seem to find it in the new project wizard…
    Thanks!

  7. sedge says:

    I’m working on a new development and decided to stick with 2.5.1 due to the difficulty of migrating 2.x plugins to 3.x. Fired up Intellij 15 and it will not accept a Grails 2 SDK. It requires Grails 3. Looks like we are stuck in Intellij 14 until there are enough Grails plugins migrated to 3.x.

  8. Salman says:

    in Idea 15 EAP — I can not Run — [ grails generate-all com.DomainClass ] or [ grails create-service com.DomainClass ] these type of command… isn’t it supported

  9. Bernie says:

    When is Grails 3.1 going to be properly supported? Services are not being detected properly and is affecting autocompletion of methods names. Same goes for domain classes. This is just very poor showing for the smarted Java IDE out there.

Leave a Reply

Your email address will not be published. Required fields are marked *