[
https://issues.apache.org/jira/browse/LUCENENET-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090345#comment-13090345
]
michael herndon commented on LUCENENET-407:
-------------------------------------------
It could have been created as a patch and that is far as its gotten.
Assuming that we're talking we're just talking about creating a simple .snk to
create strongly named assemblies when talking about signing assembly:
I didn't see a .snk file in the Lucene.Net_2_9_4g branch when setting up the
build scripts. I haven't looked in trunk yet.
The Lucene.Net_4e branch should have a already have a snk. I could add the same
snk file to trunk and the 2.9.4 branch when I go add the build scripts to the
trunk this weekend, so that all the branches are building strong assemblies.
Someone would still need to go back to the tag and create a 2.9.2 version using
the snk whenever the next release does come out.
> Signing the assembly
> --------------------
>
> Key: LUCENENET-407
> URL: https://issues.apache.org/jira/browse/LUCENENET-407
> Project: Lucene.Net
> Issue Type: Improvement
> Components: Lucene.Net Core
> Affects Versions: Lucene.Net 2.9.2, Lucene.Net 2.9.4, Lucene.Net 3.x
> Reporter: Itamar Syn-Hershko
> Fix For: Lucene.Net 2.9.4, Lucene.Net 3.x
>
> Attachments: Lucene.NET.snk, signing.patch
>
>
> For our usage of Lucene.NET we need the assembly to be signed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
