hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] elek opened a new pull request #489: HDDS-1115. Provide ozone specific top-level pom.xml
Date Fri, 15 Feb 2019 12:49:49 GMT
elek opened a new pull request #489: HDDS-1115. Provide ozone specific top-level pom.xml
URL: https://github.com/apache/hadoop/pull/489
   Ozone build process doesn't require the pom.xml in the top level hadoop directory as we
use hadoop 3.2 artifacts as parents of hadoop-ozone and hadoop-hdds. The ./pom.xml is used
only to include the hadoop-ozone/hadoop-hdds projects in the maven reactor.
   From command line, it's easy to build only the ozone artifacts:
   mvn clean install -Phdds  -am -pl :hadoop-ozone-dist  -Danimal.sniffer.skip=true  -Denforcer.skip=true
   Where: '-pl' defines the build of the hadoop-ozone-dist project
   and '-am' defines to build all of the dependencies from the source tree (hadoop-ozone-common,
hadoop-hdds-common, etc.)
   But this filtering is available only from the command line.
   With providing a lightweight pom.ozone.xml we can achieve the same:
    * We can open only hdds/ozone projects in the IDE/intellij. It makes the development faster
as IDE doesn't need to reindex all the sources all the time + it's easy to execute checkstyle/findbugs
plugins of the intellij to the whole project.
    * Longer term we should create an ozone specific source artifact (currently the source
artifact for hadoop and ozone releases are the same) which also requires a simplified pom.
   In this patch I also added the .mvn directory to the .gitignore file.
   mkdir -p .mvn && echo "-f ozone.pom.xml" > .mvn/maven.config" you can persist
the usage of the ozone.pom.xml for all the subsequent builds (in the same dir)
   How to test?
   Just do a 'mvn -f ozonze.pom.xml clean install -DskipTests'
   See: https://issues.apache.org/jira/browse/HDDS-1115

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message