[
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036640#comment-13036640
]
Todd Lipcon commented on HADOOP-6671:
-------------------------------------
Cool stuff, Alejandro! A few things I noticed while trying this out locally:
- nit: The project name is "Hadoop Common" rather than "Hadoop Commons"
- I'm getting errors for our usage of the com.sun.javadoc stuff - eg:
{code}
/home/todd/git/hadoop-common/src/main/java/org/apache/hadoop/classification/tools/ExcludePrivateAnnotationsJDiffDoclet.java:[42,16]
cannot access com.sun.javadoc.Doclet
class file for com.sun.javadoc.Doclet not found
return JDiff.start(RootDocProcessor.process(root));
/home/todd/git/hadoop-common/src/main/java/org/apache/hadoop/classification/tools/RootDocProcessor.java:[55,12]
cannot find symbol
{code}
Is this the bit where I need to add a softlink? Any workaround for this we can
do local to the project?
- "mvn test" seems to be dumping all the log to stdout. Is there a way to get
it to log just to the files like ant used to?
- is there an equivalent of our "bin-package" target which makes a tarball but
doesn't build the forrest docs?
- the assembly doesn't seem to build if I choose not to compile native:
{code}
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] An Ant BuildException has occured:
/home/todd/git/hadoop-common/target/native/lib does not exist.
{code}
> 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
> Attachments: HADOOP-6671.patch, build.png,
> hadoop-commons-maven.patch, mvn-layout.sh, mvn-layout.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
