hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Charles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-6671) To use maven for hadoop common builds
Date Sun, 12 Jun 2011 09:59:52 GMT

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

Eric Charles commented on HADOOP-6671:

Jenkins haddop-common-trunk is blue (builds fine).
I've downloaded https://builds.apache.org/job/Hadoop-Common-trunk-maven/13/artifact/trunk/target/hadoop-common-0.23.0-SNAPSHOT.tar.gz
and imported it in eclipse via m2eclipse. Still need to add 3 folders in my build path to
have operation project in eclipse: target/generated-sources/avro-protocol, avro-schema and
record-cc (Maybe this can be solved with the build-helper-maven-plugin : http://www.sonatype.com/people/2008/05/adding-additional-source-folders-to-your-maven-build/)

When I run "mvn test" in shell, I've got two failures in TestUserGroupInformation [1], however
the TestUserGroupInformation run from eclipse works fine.
Seems like UserGroupInformation behaves differently in shell than in eclipse. Same issue if
I run "mvn test -P os.mac" (I run on mac).

Test set: org.apache.hadoop.security.TestUserGroupInformation
Tests run: 14, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.389 sec <<< FAILURE!
testGetServerSideGroups(org.apache.hadoop.security.TestUserGroupInformation)  Time elapsed:
0.029 sec  <<< FAILURE!
java.lang.AssertionError: expected:<13> but was:<0>
	at org.junit.Assert.fail(Assert.java:91)
	at org.junit.Assert.failNotEquals(Assert.java:645)
	at org.junit.Assert.assertEquals(Assert.java:126)
	at org.junit.Assert.assertEquals(Assert.java:470)
	at org.junit.Assert.assertEquals(Assert.java:454)
	at org.apache.hadoop.security.TestUserGroupInformation.testGetServerSideGroups(TestUserGroupInformation.java:97)
testLogin(org.apache.hadoop.security.TestUserGroupInformation)  Time elapsed: 0 sec  <<<
	at org.junit.Assert.fail(Assert.java:91)
	at org.junit.Assert.assertTrue(Assert.java:43)
	at org.junit.Assert.assertTrue(Assert.java:54)
	at org.apache.hadoop.security.TestUserGroupInformation.testLogin(TestUserGroupInformation.java:122)

> To use maven for hadoop common builds
> -------------------------------------
>                 Key: HADOOP-6671
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6671
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 0.22.0
>            Reporter: Giridharan Kesavan
>            Assignee: Alejandro Abdelnur
>         Attachments: HADOOP-6671-cross-project-HDFS.patch, HADOOP-6671-e.patch, HADOOP-6671.patch,
HADOOP-6671b.patch, HADOOP-6671c.patch, HADOOP-6671d.patch, build.png, hadoop-commons-maven.patch,
mvn-layout-e.sh, mvn-layout.sh, mvn-layout.sh, mvn-layout2.sh, mvn-layout2.sh
> We are now able to publish hadoop artifacts to the maven repo successfully [ Hadoop-6382]
> Drawbacks with the current approach:
> * Use ivy for dependency management with ivy.xml
> * Use maven-ant-task for artifact publishing to the maven repository
> * pom files are not generated dynamically 
> To address this I propose we use maven to build hadoop-common, which would help us to
manage dependencies, publish artifacts and have one single xml file(POM) for dependency management
and artifact publishing.
> I would like to have a branch created to work on mavenizing  hadoop common.

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


View raw message