Announcement Announcement Module
Collapse
No announcement yet.
GGTS 3.0.0 grails-maven-plugin:2.1.0:validate-plugin error Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • GGTS 3.0.0 grails-maven-plugin:2.1.0:validate-plugin error

    Using GGTS 3.0.0 with the m2e extension and Grails 2.1.0, I imported a previously mavenized grails project (also configured to use Grails 2.1.0; works fine using mvn commands on command-line). It fails to compile in the IDE with the following errors:

    * Plugin execution not covered by lifecycle configuration: org.grails:grails-maven-plugin:2.1.0:config-directories (execution: default, phase: generate-sources)
    * Plugin execution not covered by lifecycle configuration: org.grails:grails-maven-plugin:2.1.0:maven-compile (execution: default-maven-compile, phase: compile)
    * Plugin execution not covered by lifecycle configuration: org.grails:grails-maven-plugin:2.1.0:init (execution: default, phase: initialize)
    * Plugin execution not covered by lifecycle configuration: org.grails:grails-maven-plugin:2.1.0:config-directories (execution: default-config-directories, phase: generate-sources)
    * Plugin execution not covered by lifecycle configuration: org.grails:grails-maven-plugin:2.1.0:maven-compile (execution: default, phase: compile)
    * Plugin execution not covered by lifecycle configuration: org.grails:grails-maven-plugin:2.1.0:validate-plugin (execution: default-validate-plugin, phase: validate)
    * Plugin execution not covered by lifecycle configuration: org.grails:grails-maven-plugin:2.1.0:init-plugin (execution: default-init-plugin, phase: initialize)
    * Plugin execution not covered by lifecycle configuration: org.grails:grails-maven-plugin:2.1.0:validate (execution: default, phase: validate)

    Is there some configuration magic that will fix this? thanks...

  • #2
    Generalized my search string and found more relevant stuff:
    http://stackoverflow.com/questions/7...-configuration
    http://blog.springsource.com/2011/10...l-suite-2-8-0/
    http://wiki.eclipse.org/M2E_plugin_e...on_not_covered
    http://forum.springsource.org/showth...eedback-sought

    Based on this information, I set m2e to ignore the plugins - compile finished. Then I set m2e to execute the plugins - compile still finished.

    Is this the recommended solution? Are there any plans afoot to create m2e project configurators for these maven-grails-plugin goals? Is there actually a way to run "mvn grails:*" commands through GGTS?
    Last edited by John Holme; Aug 16th, 2012, 05:16 PM.

    Comment


    • #3
      Hi John,

      I'm afraid we don't have immediate plans to provide plugins to handle those situations - ignoring plugins will obviously only be doing the right thing if you didn't need those plugins to do anything. We know the grails/maven story is less than ideal and we have an umbrella jira covering improving the support for this setup: https://issuetracker.springsource.com/browse/STS-596 - you might want to comment/vote on that. It is our most voted for issue so it is coming onto the radar for active development. Interestingly the jira isn't discussing the missing lifecycle configurators, that should be added, I think the jira was raised before the latest m2e came along that introduced the 'plugin execution not covered by lifecycle configuration' problem.

      cheers,
      Andy

      Comment


      • #4
        thanks Andy. I posted to the springsource issue tracker.

        Comment

        Working...
        X