hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laxman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7660) Maven generated .classpath doesnot includes "target/generated-test-source/java" as source directory.
Date Thu, 22 Sep 2011 05:39:27 GMT

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

Laxman commented on HADOOP-7660:
--------------------------------

{quote}-1 release audit. The applied patch generated 1 release audit warnings (more than the
trunk's current 0 warnings).

/home/jenkins/jenkins-slave/workspace/PreCommit-HADOOP-Build/trunk/hadoop-common-project/hadoop-common/src/main/packages/templates/conf/log4j.properties
Lines that start with ????? in the release audit report indicate files that do not have an
Apache license header.
{quote}

This doesn't seems to be caused by this patch. Any idea?

{quote}
-1 tests included.
{quote}

Patch involves build script[pom.xml] changes only.

> Maven generated .classpath doesnot includes "target/generated-test-source/java" as source
directory.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-7660
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7660
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.24.0
>            Reporter: Laxman
>            Priority: Minor
>              Labels: eclipse, maven
>             Fix For: 0.24.0, HA Branch (HDFS-1623)
>
>         Attachments: HADOOP-7660.patch
>
>
> I can see lot of compilation issues after setting up my development environment using
"mvn eclipse:eclipse". All these compilation issues are resolved after adding "target/generated-test-sources"
as a source folder to the common project.
> When verified the "pom.xml", it's noticed that these are included under "generate-test-sources"
phase. This seems to be a problem occurred because of incorrect understanding/usage of "build-helper-maven-plugin"
in Common project.
> All these compilation issues are resolved after changing the phase to "generate-sources".
> I found similar issue here.
> https://issues.sonatype.org/browse/MNGECLIPSE-2387

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message