Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gmavenplus-plus plugin execution not covered since 1.6 #340

Closed
papegaaij opened this issue Sep 19, 2017 · 5 comments
Closed

gmavenplus-plus plugin execution not covered since 1.6 #340

papegaaij opened this issue Sep 19, 2017 · 5 comments

Comments

@papegaaij
Copy link

In groovy/GMavenPlus#31 several goals were renamed. For example, testCompile is now compileTests. This causes errors like Plugin execution not covered by lifecycle configuration: org.codehaus.gmavenplus:gmavenplus-plugin:1.6:compileTests (execution: default, phase: test-compile).

@eric-milles
Copy link
Member

Not sure if I follow. Is this a request to change something in groovy-eclipse-batch or groovy-eclipse-compiler artifacts?

@missedone
Copy link

missedone commented Sep 20, 2017

if I read correct, @papegaaij means there need a fix in the default m2e lifecycle-mapping xml:
https://github.com/groovy/groovy-eclipse/blob/master/extras/org.codehaus.groovy.m2eclipse/lifecycle-mapping-metadata.xml#L67

looks like you need to define two portions, one is for <versionRange>[1.0,1.6)</versionRange>, and the other is for <versionRange>[1.6,)</versionRange>

@papegaaij
Copy link
Author

What @missedone says. The lifecycle-mapping needs to be realligned with the new names of the goals. I'm not sure if this only applies to the lifecycle-mapping-metadata.xml. Maybe those names also show up in other parts of the code. For example, https://github.com/groovy/groovy-eclipse/blob/master/extras/org.codehaus.groovy.m2eclipse/src/org/codehaus/groovy/m2eclipse/ProjectSourceType.java#L95 also seems to refer to this goal name.

@eric-milles
Copy link
Member

Sorry, I looked at the actual commits attached to the linked issue instead of the comments and have this instead:

    <pluginExecution>
      <pluginExecutionFilter>
        <groupId>org.codehaus.gmavenplus</groupId>
        <artifactId>gmavenplus-plugin</artifactId>
        <versionRange>[1.0,1.6)</versionRange>
        <goals>
          <goal>addSources</goal>
          <goal>addTestSources</goal>
          <goal>generateStubs</goal>
          <goal>compile</goal>
          <goal>removeStubs</goal>
          <goal>testGenerateStubs</goal>
          <goal>testCompile</goal>
          <goal>removeTestStubs</goal>
        </goals>
        </pluginExecutionFilter>
        <action>
          <configurator>
            <id>org.codehaus.groovy.m2eclipse.configurator</id>
          </configurator>
        </action>
    </pluginExecution>
    <pluginExecution>
      <pluginExecutionFilter>
        <groupId>org.codehaus.gmavenplus</groupId>
        <artifactId>gmavenplus-plugin</artifactId>
        <versionRange>[1.6,)</versionRange>
        <goals>
          <goal>addSources</goal>
          <goal>addTestSources</goal>
          <goal>generateStubs</goal>
          <goal>compile</goal>
          <goal>removeStubs</goal>
          <goal>generateTestStubs</goal>
          <goal>compileTests</goal>
          <goal>removeTestStubs</goal>
        </goals>
        </pluginExecutionFilter>
        <action>
          <configurator>
            <id>org.codehaus.groovy.m2eclipse.configurator</id>
          </configurator>
        </action>
    </pluginExecution>
  </pluginExecutions>

@papegaaij
Copy link
Author

This change looks ok to me. In just over a week I'll have a chance to try updating again. If something else needs to be done, I'll report back. Thanks for the quick response.

based2 added a commit to based2/shiro that referenced this issue Feb 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants