[
https://issues.apache.org/jira/browse/MARMOTTA-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14015278#comment-14015278
]
ASF subversion and git services commented on MARMOTTA-485:
----------------------------------------------------------
Commit aa8615114f9f6b7999baa37b4c04f2c9ce257fa8 in marmotta's branch
refs/heads/develop from [~jakob]
[ https://git-wip-us.apache.org/repos/asf?p=marmotta.git;h=aa86151 ]
MARMOTTA-485: moved LinkedData CLI into a separate module that is not
deployed/installed to the maven repo
(but contains the CLI bundle)
> Signatures are not automatically generated for ldpath tarballs
> --------------------------------------------------------------
>
> Key: MARMOTTA-485
> URL: https://issues.apache.org/jira/browse/MARMOTTA-485
> Project: Marmotta
> Issue Type: Bug
> Components: Build Environment
> Affects Versions: 3.2.0
> Reporter: Sergio Fernández
> Assignee: Jakob Frank
> Priority: Critical
> Labels: gpg, maven
> Fix For: 3.3.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Checking the 3.2.0 release we have realized that the work performed for
> solving MARMOTTA-339 did not completely solved the issue. It looks that
> detaching those binaries for the assembly makes them not eligible for signing.
> The quick fix for now is to manually generate those signatures, see r5011 at
> dist.apache.org
--
This message was sent by Atlassian JIRA
(v6.2#6252)
