hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8094) Make maven-eclipse-plugin use the spring project nature
Date Mon, 20 Feb 2012 17:35:34 GMT

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

Hadoop QA commented on HADOOP-8094:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/614//console

This message is automatically generated.
> Make maven-eclipse-plugin use the spring project nature
> -------------------------------------------------------
>                 Key: HADOOP-8094
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8094
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 0.23.0
>            Reporter: Harsh J
>            Assignee: Harsh J
>              Labels: eclipse, maven
>         Attachments: HADOOP-8094.patch
> If I want to have multiple versions of Apache Hadoop loaded into my Eclipse IDE today
(or any other IDE maybe), I'm supposed to do the following when generating eclipse files,
such that the version name is appended to the project name and thereby resolves conflict in
project names when I import another version in:
> {{mvn -Declipse.addVersionToProjectName=true eclipse:eclipse}}
> But this does not work presently due to a lack of configuration in Apache Hadoop, which
https://jira.codehaus.org/browse/MECLIPSE-702 demands. The problem being that though the project
names are indeed named with version suffixes, the "related project" name it carries for dependencies
do not carry the same suffix and therefore you have a broken import of projects errors everywhere
about 'dependent project <regularname> not found'.
> The fix is as Carlo details on https://jira.codehaus.org/browse/MECLIPSE-702 and it works
perfectly. I'll attach a patch adding in the same configuration for Apache Hadoop so that
the above mechanism is then possible.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message