hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-13236) Clean up m2e-related warnings/errors from poms
Date Sat, 14 Mar 2015 02:47:38 GMT

     [ https://issues.apache.org/jira/browse/HBASE-13236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Josh Elser updated HBASE-13236:
    Attachment: HBASE-13236-v1.patch

Wrapped comment lines that exceeded 80chars. Was _slightly_ over-aggressive in the top-level
pom.xml as the comment block I added to already exceeded 80 chars.

> 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.1.0
>         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

View raw message