hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Yates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8108) Add m2eclispe lifecycle mapping to hbase-commn
Date Thu, 14 Mar 2013 17:54:13 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602494#comment-13602494

Jesse Yates commented on HBASE-8108:

Given that eclipse and intellij are the main two tools  by a large fraction (I doubt many
people are hacking HBase with a basic text editor), this isn't all that unreasonable...especially
as we have done this in the code before. IMO supporting the most widely used tools well is
not only good, its nearly mandatory.
> Add m2eclispe lifecycle mapping to hbase-commn
> ----------------------------------------------
>                 Key: HBASE-8108
>                 URL: https://issues.apache.org/jira/browse/HBASE-8108
>             Project: HBase
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.95.0, 0.98.0
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>         Attachments: hbase-8108.patch
> The maven-antrun-plugin execution doesn't have a default mapping in m2eclipse, so if
you import the project into eclipse, you will get an error that the mapping is undefined.
All that's needed is to define an execution via the org.eclipse.m2 lifecycle-mapping plugin
- it doesn't actually affect the usual maven build at all.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message