[
https://issues.apache.org/jira/browse/HBASE-18593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126351#comment-16126351
]
Hudson commented on HBASE-18593:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3532 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3532/])
HBASE-18593 Tell m2eclipse what to do w/ replacer plugin (stack: rev
bd40073094b248f74ac9a3c0fff7ef6668265feb)
* (edit) hbase-protocol-shaded/pom.xml
> Tell m2eclipse what to do w/ replacer plugin
> --------------------------------------------
>
> Key: HBASE-18593
> URL: https://issues.apache.org/jira/browse/HBASE-18593
> Project: HBase
> Issue Type: Sub-task
> Components: build
> Reporter: stack
> Assignee: stack
> Priority: Trivial
> Fix For: 2.0.0
>
>
> 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:
> {code}
> 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>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
