You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2018/12/01 14:46:00 UTC

[jira] [Commented] (UIMA-5917) fix publish of signed Eclipse Jars for 3.0.1 and 2.10.3

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

Marshall Schor commented on UIMA-5917:
--------------------------------------

The thing that went wrong: we switched from generating md5/sha1 to sha512.  But the old md5/sha1 files were not removed, and no longer "match" the artifacts.  Fix: just remove the old files (they have old dates)

> fix publish of signed Eclipse Jars for 3.0.1 and 2.10.3
> -------------------------------------------------------
>
>                 Key: UIMA-5917
>                 URL: https://issues.apache.org/jira/browse/UIMA-5917
>             Project: UIMA
>          Issue Type: Task
>          Components: Eclipse plugins
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Major
>
> Investigate what went wrong with adding md5 and sha1 signatures after Eclipse Jar signing. 
>  Fix the published site.  Test if site works without sha1 and md5 for installing Eclipse plugins.



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