You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2014/04/04 00:03:16 UTC
[jira] [Commented] (ACCUMULO-2626) the dist tarball deployed to the
staging repo is not the same dist tarball built by assembly plugin
[ https://issues.apache.org/jira/browse/ACCUMULO-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959309#comment-13959309 ]
Christopher Tubbs commented on ACCUMULO-2626:
---------------------------------------------
I think maybe this contains two issues: 1) the tarballs are not the same, and 2) the tarballs don't contain the jars whose gpg signatures have been verified.
> the dist tarball deployed to the staging repo is not the same dist tarball built by assembly plugin
> ---------------------------------------------------------------------------------------------------
>
> Key: ACCUMULO-2626
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2626
> Project: Accumulo
> Issue Type: Bug
> Components: build
> Affects Versions: 1.4.5
> Reporter: Mike Drob
>
> the dist tarball
> deployed to the staging repo is not the same dist tarball as the one
> deployed to the people. The one deployed to maven does not contain the
> apidocs or several libs. In addition, the jars deployed to maven are
> not the same jars included in the dist tarball (may be functionally
> equivalent, but are not binary equivalent).
--
This message was sent by Atlassian JIRA
(v6.2#6252)