Details

      Description

      For our usage of Lucene.NET we need the assembly to be signed.

      1. Lucene.NET.snk
        0.6 kB
        Itamar Syn-Hershko
      2. signing.patch
        2 kB
        Itamar Syn-Hershko

        Issue Links

          Activity

          Hide
          Itamar Syn-Hershko added a comment -

          snk file and a patch to apply signing

          Show
          Itamar Syn-Hershko added a comment - snk file and a patch to apply signing
          Hide
          Troy Howard added a comment -

          This is an exact duplicate of open issue LUCENENET-389.

          Show
          Troy Howard added a comment - This is an exact duplicate of open issue LUCENENET-389 .
          Hide
          Troy Howard added a comment -

          Unable to apply this current 2.9.2 release, as it's already post release.

          We could include a signed 2.9.2 build with the 2.9.4 release, but that build would have to be made from the 2.9.2 source.

          Show
          Troy Howard added a comment - Unable to apply this current 2.9.2 release, as it's already post release. We could include a signed 2.9.2 build with the 2.9.4 release, but that build would have to be made from the 2.9.2 source.
          Hide
          Itamar Syn-Hershko added a comment -

          That would work, thanks.

          Show
          Itamar Syn-Hershko added a comment - That would work, thanks.
          Hide
          Itamar Syn-Hershko added a comment -

          Hmm... I just looked around the branches and couldn't see this committed anywhere. Ideas?

          Show
          Itamar Syn-Hershko added a comment - Hmm... I just looked around the branches and couldn't see this committed anywhere. Ideas?
          Hide
          michael herndon added a comment -

          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.

          Show
          michael herndon added a comment - 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.
          Hide
          Prescott Nasser added a comment -

          Michael added the necessary .snk files so that code can be compiled and signed by those who need it. We did not include a specifically signed version of the code

          Show
          Prescott Nasser added a comment - Michael added the necessary .snk files so that code can be compiled and signed by those who need it. We did not include a specifically signed version of the code

            People

            • Assignee:
              michael herndon
              Reporter:
              Itamar Syn-Hershko
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved:

                Development