hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elek, Marton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-1734) Use maven assembly to create ozone tarball image
Date Tue, 02 Jul 2019 00:32:00 GMT

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

Elek, Marton commented on HDDS-1734:
------------------------------------

{quote} This prevents down stream project to use Ozone tarball as a dependency.  It would
be nice to create Ozone tarball with maven assembly plugin to have ability to cache ozone
tarball in maven repository.
{quote}
There is no down stream project who would like to use the tarbal. In fact even hadoop has
no downstream project which consumes tar files. This use case doesn't seem to be realistic
for me (at least now)
{quote}This change can help docker development to be more agile without making a full project
build.
{quote}
You can do it even now:
{code:java}
cd hadoop-ozone/dist
mvn docker:build -Pdocker-build{code}
 

I agree with [~anu]: It makes the build (and release) slower and consumes more space. And
I can't see any immediate technical benefit.

> Use maven assembly to create ozone tarball image
> ------------------------------------------------
>
>                 Key: HDDS-1734
>                 URL: https://issues.apache.org/jira/browse/HDDS-1734
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>            Priority: Major
>         Attachments: HDDS-1734.001.patch, HDDS-1734.002.patch, HDDS-1734.003.patch
>
>
> Ozone is using tar stitching to create ozone tarball.  This prevents down stream project
to use Ozone tarball as a dependency.  It would be nice to create Ozone tarball with maven
assembly plugin to have ability to cache ozone tarball in maven repository.  This ability
allows docker build to be a separate sub-module and referencing to Ozone tarball.  This
change can help docker development to be more agile without making a full project build.
> Test procedure:
> {code:java}
> mvn -f pom.ozone.xml clean install -DskipTests -DskipShade -Dmaven.javadoc.skip -Pdist{code}
> Expected result:
> This will install tarball into:
> {code:java}
> ~/.m2/repository/org/apache/hadoop/hadoop-ozone-dist/0.5.0-SNAPSHOT/hadoop-ozone-dist-0.5.0-SNAPSHOT.tar.gz{code}
> Test procedure 2:
> {code:java}
> mvn -f pom.ozone.xml clean package -DskipTests -DskipShade -Dmaven.javadoc.skip -Pdist{code}
>  
> Expected result:
> hadoop/hadoop-ozone/dist/target directory contains ozone-0.5.0-SNAPSHOT.tar.gz file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message