You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucenenet.apache.org by "Troy Howard (JIRA)" <ji...@apache.org> on 2011/02/21 17:41:38 UTC

[Lucene.Net] [jira] Updated: (LUCENENET-389) Ensure that released assembly is a signed Strong Named Assembly

     [ https://issues.apache.org/jira/browse/LUCENENET-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Troy Howard updated LUCENENET-389:
----------------------------------

    Priority: Major  (was: Critical)
     Summary: Ensure that released assembly is a signed Strong Named Assembly  (was: Signing the released assembly)

> Ensure that released assembly is a signed Strong Named Assembly
> ---------------------------------------------------------------
>
>                 Key: LUCENENET-389
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-389
>             Project: Lucene.Net
>          Issue Type: Improvement
>          Components: Lucene.Net Core
>    Affects Versions: Lucene.Net 2.9.4
>            Reporter: Patric Forsgard
>             Fix For: Lucene.Net 2.9.4
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the project I working in i need a signed version of the Lucene.Net-assembly. For the moment I will compile and sign with my own key but it would be great if the official release already should be signed.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira