You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Patric Forsgard (JIRA)" <ji...@apache.org> on 2011/01/21 22:33:44 UTC
[jira] Created: (LUCENENET-389) Signing the released assembly
Signing the released assembly
-----------------------------
Key: LUCENENET-389
URL: https://issues.apache.org/jira/browse/LUCENENET-389
Project: Lucene.Net
Issue Type: Wish
Reporter: Patric Forsgard
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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (LUCENENET-389) Signing the released assembly
Posted by "Scott Lombard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Lombard updated LUCENENET-389:
------------------------------------
Component/s: Lucene.Net Core
Due Date: 28/Feb/11
Priority: Critical (was: Major)
Affects Version/s: Lucene.Net 2.9.2
Fix Version/s: Lucene.Net 2.9.2
Issue Type: Improvement (was: Wish)
Remaining Estimate: 16h
Original Estimate: 16h
> Signing the released 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.2
> Reporter: Patric Forsgard
> Priority: Critical
> Fix For: Lucene.Net 2.9.2
>
> Original Estimate: 16h
> Remaining Estimate: 16h
>
> 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
[jira] Commented: (LUCENENET-389) Signing the released assembly
Posted by "Digy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984957#action_12984957 ]
Digy commented on LUCENENET-389:
--------------------------------
You are right. We should think of signing Lucene.Net when we get an official release.
DIGY
> Signing the released assembly
> -----------------------------
>
> Key: LUCENENET-389
> URL: https://issues.apache.org/jira/browse/LUCENENET-389
> Project: Lucene.Net
> Issue Type: Wish
> Reporter: Patric Forsgard
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[Lucene.Net] [jira] Updated: (LUCENENET-389) Ensure that released assembly is a
signed Strong Named Assembly
Posted by "Troy Howard (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (LUCENENET-389) Signing the released assembly
Posted by "Troy Howard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Troy Howard updated LUCENENET-389:
----------------------------------
Due Date: 28/Mar/11 (was: 28/Feb/11)
> Signing the released 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
> 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: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-389) Signing the released assembly
Posted by "Troy Howard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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:
http://msdn.microsoft.com/en-us/library/wd40t7ad.aspx
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: 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
> 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: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Resolved] (LUCENENET-389) Ensure that released assembly is
a signed Strong Named Assembly
Posted by "Prescott Nasser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LUCENENET-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prescott Nasser resolved LUCENENET-389.
---------------------------------------
Resolution: Duplicate
> 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