[
https://issues.apache.org/jira/browse/HBASE-13236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361634#comment-14361634
]
Hudson commented on HBASE-13236:
--------------------------------
FAILURE: Integrated in HBase-0.98 #899 (See
[https://builds.apache.org/job/HBase-0.98/899/])
HBASE-13236 Add addt'l lifecycle-mapping executions. (busbey: rev
8f034815f661469d258618efde393366a36a27e5)
* hbase-examples/pom.xml
* pom.xml
* hbase-it/pom.xml
* hbase-hadoop2-compat/pom.xml
* hbase-server/pom.xml
* hbase-rest/pom.xml
* hbase-shell/pom.xml
* hbase-prefix-tree/pom.xml
* hbase-client/pom.xml
* hbase-common/pom.xml
* hbase-thrift/pom.xml
* hbase-hadoop-compat/pom.xml
> Clean up m2e-related warnings/errors from poms
> ----------------------------------------------
>
> Key: HBASE-13236
> URL: https://issues.apache.org/jira/browse/HBASE-13236
> Project: HBase
> Issue Type: Improvement
> Components: build
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Minor
> Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.12
>
> Attachments: HBASE-13236-master.patch, HBASE-13236-v1.patch
>
>
> Pulled down HBase, imported into Eclipse (either directly with m2eclipse or
> by running {{mvn eclipse:eclipse}} to generate the projects), and this
> results in a bunch of red due to executions/goals of certain plugins being
> unable to run in the context of eclipse.
> The lifecycle-mapping "plugin" can be used to get around these errors (and
> already exists in the pom).
> Add more mappings to the configuration so that a fresh import into Eclipse is
> not hindered by a bunch of "false' errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
