Details

    • Sub-task
    • Status: Resolved
    • Trivial
    • Resolution: Fixed
    • None
    • 2.0.0
    • build
    • None

    Description

      Tripped over this playing w/ eclipse today. The mvn maven-replacer-plugin plugin that we added to hbase-protocol-shaded triggers outside usual lifecycle. The newer m2eclipse plugins need to be told explicitly what to do w/ plugins of this type. Let me commit this:

      diff --git a/hbase-protocol-shaded/pom.xml b/hbase-protocol-shaded/pom.xml
      index b28c03e740..4c72ecaa93 100644
      --- a/hbase-protocol-shaded/pom.xml
      +++ b/hbase-protocol-shaded/pom.xml
      @@ -192,6 +192,23 @@
                           <ignore/>
                         </action>
                       </pluginExecution>
      +                <pluginExecution>
      +                  <pluginExecutionFilter>
      +                    <groupId>
      +                      com.google.code.maven-replacer-plugin
      +                    </groupId>
      +                    <artifactId>replacer</artifactId>
      +                    <versionRange>[1.5.3,)</versionRange>
      +                    <goals>
      +                      <goal>replace</goal>
      +                    </goals>
      +                  </pluginExecutionFilter>
      +                  <action>
      +                    <execute>
      +                     <runOnIncremental>false</runOnIncremental>
      +                    </execute>
      +                  </action>
      +                </pluginExecution>
                     </pluginExecutions>
                   </lifecycleMappingMetadata>
                 </configuration>
      

      Attachments

        Activity

          People

            stack Michael Stack
            stack Michael Stack
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: