lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Troy Howard (JIRA)" <>
Subject [jira] Updated: (LUCENENET-389) Signing the released assembly
Date Sun, 20 Feb 2011 03:00:38 GMT


Troy Howard updated LUCENENET-389:

     Affects Version/s:     (was: Lucene.Net 2.9.2)
                        Lucene.Net 2.9.4
         Fix Version/s:     (was: Lucene.Net 2.9.2)
                        Lucene.Net 2.9.4
    Remaining Estimate: 1h  (was: 16h)
     Original Estimate: 1h  (was: 16h)

Scheduled for 2.9.4 release. The signing requested here is not part of the normal release
process. It's in reference to created a Strong Named Assembly, generally so that a DLL may
be included in the GAC. 

See here:

The normal Apache binary releases are signed, but that's a different process, and more focused
on verification of the source/creator of the assembly. 

Because this can't be built from the current 2.9.2 tag without modifications, we'll need to
push this out to the 2.9.4 release. 

> Signing the released assembly
> -----------------------------
>                 Key: LUCENENET-389
>                 URL:
>             Project: Lucene.Net
>          Issue Type: Improvement
>          Components: Lucene.Net Core
>    Affects Versions: Lucene.Net 2.9.4
>            Reporter: Patric Forsgard
>            Priority: Critical
>             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:


View raw message