[jira] [Comment Edited] (NIFI-5402) Reduce artifact size by only building .zip archive

["Kevin Doran (JIRA)" <ji...@apache.org>]

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

Kevin Doran edited comment on NIFI-5402 at 10/12/18 3:42 PM:
-------------------------------------------------------------

-Currently, the Dockerfiles for the nifi and nifi-toolkit images require the .tag.gz binaries for published versions. I think there was some discussion on the mailing list about this a while back, but do we have a solution for this so that we don't break our Dockerfiles?-

Disregard, it looks like there was a PR to address this. See NIFI-5468 and the mailing list discussion below.


was (Author: kdoran):
Currently, the Dockerfiles for the nifi and nifi-toolkit images require the .tag.gz binaries for published versions. I think there was some discussion on the mailing list about this a while back, but do we have a solution for this so that we don't break our Dockerfiles?

> Reduce artifact size by only building .zip archive
> --------------------------------------------------
>
>                 Key: NIFI-5402
>                 URL: https://issues.apache.org/jira/browse/NIFI-5402
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Tools and Build
>    Affects Versions: 1.7.0
>            Reporter: Andy LoPresto
>            Assignee: Nathan Gough
>            Priority: Major
>              Labels: archive, build, format, maven, tar, zip
>
> The maven build bundles two identical builds (one in .tar.gz format and one in .zip format). Based on community discussion, there is no longer a need for separate .tar.gz, and removing this would increase the speed of the build and greatly decrease the hosting requirements for the binaries. 
> That said, building a .tar.gz archive should be available through an (inactive) profile if a user wants to enable it. 



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