Directory Studio
  1. Directory Studio
  2. DIRSTUDIO-821

Where to get the public certificate used to sign the JAR of DS 1.5.3?

    Details

      Description

      Hello,

      2 questions, actually.
      1/ I would like to ship ADS 1.5.3 into an Eclipse RCP application I'm writing: may I? This app is also released under the Apache Licence.
      2/ I cannot generate the P2 metadata of my app if I embed ADS. I think this is because the public certificate of the certificate used to sign the pug-in JAR files is not present in my JDK cacerts file. Where to get this public certificate? For information, the one I'm interested in expired on 31/01/10 18:28

      Thanks

        Activity

        Hide
        Pierre-Arnaud Marcelot added a comment -

        Hi Super Nounouille (joli surnom! )

        1°/ That's completely OK, it's covered by the Apache License. Feel free to do so but just make sure to follow what's stated in the License file and update the NOTICE file as mentioned in §4.(d).
        Reading those pages might also help:

        2°/ May advise you to prefer the 2.0.0-M3 version? It's the most recent one and even if it has a 'Milestone' badge, it is clearly less buggy than 1.5.3.
        And, it isn't signed by any certificate so, this would probably solve your p2 repository generation.

        Show
        Pierre-Arnaud Marcelot added a comment - Hi Super Nounouille (joli surnom! ) 1°/ That's completely OK, it's covered by the Apache License. Feel free to do so but just make sure to follow what's stated in the License file and update the NOTICE file as mentioned in §4.(d). Reading those pages might also help: http://www.apache.org/licenses/ http://www.apache.org/foundation/license-faq.html 2°/ May advise you to prefer the 2.0.0-M3 version? It's the most recent one and even if it has a 'Milestone' badge, it is clearly less buggy than 1.5.3. And , it isn't signed by any certificate so, this would probably solve your p2 repository generation.
        Hide
        Super Nounouille added a comment -

        Hello,

        Thanks for the reply.

        I'm not very comfortable with the licence stuff, especially the NOTICE. I'd like to add one but my English is not "legal" enough to understand what I'm supposed to put in this file. The license page shows an example taken from the httpd server, but I don't understand how I could convert it to my case.

        Anyway, I'm on the process of integrating 2.0.0-M3. Doing so, I have noticed some inconsistencies between dependencies when I am updating my plugin target platform in the Eclipse preferences. The LDAP browser feature declares the following dependencies toward plugins that can be found on the update site but with invalid bundle versions (Bundle-Version in MANIFEST.MF):
        Required plugin, version => Bundle-Version found in the plugin of the update site
        org.apache.commons.codec, 1.6 => 1.6.0 (org.apache.commons.codec_1.6.0.jar)
        org.bouncycastle.bcprov.jdk15, 140 => 140.0.0 (org.bouncycastle.bcprov.jdk15_140.0.0.jar)
        org.apache.commons.io, 2.1 => 2.1.0 (org.apache.commons.io_2.1.0.jar)
        org.apache.commons.lang, 2.6 => 2.6.0 (org.apache.commons.lang_2.6.0.jar)

        Thanks,

        Show
        Super Nounouille added a comment - Hello, Thanks for the reply. I'm not very comfortable with the licence stuff, especially the NOTICE. I'd like to add one but my English is not "legal" enough to understand what I'm supposed to put in this file. The license page shows an example taken from the httpd server, but I don't understand how I could convert it to my case. Anyway, I'm on the process of integrating 2.0.0-M3. Doing so, I have noticed some inconsistencies between dependencies when I am updating my plugin target platform in the Eclipse preferences. The LDAP browser feature declares the following dependencies toward plugins that can be found on the update site but with invalid bundle versions (Bundle-Version in MANIFEST.MF): Required plugin, version => Bundle-Version found in the plugin of the update site org.apache.commons.codec, 1.6 => 1.6.0 (org.apache.commons.codec_1.6.0.jar) org.bouncycastle.bcprov.jdk15, 140 => 140.0.0 (org.bouncycastle.bcprov.jdk15_140.0.0.jar) org.apache.commons.io, 2.1 => 2.1.0 (org.apache.commons.io_2.1.0.jar) org.apache.commons.lang, 2.6 => 2.6.0 (org.apache.commons.lang_2.6.0.jar) Thanks,
        Hide
        Super Nounouille added a comment -

        Hello,

        In order to be able to incorporate 2.0.0-M3 into my app I also had to set a version to the exported packages of org.apache.commons.logging_1.1.1.jar

        Regards,

        Show
        Super Nounouille added a comment - Hello, In order to be able to incorporate 2.0.0-M3 into my app I also had to set a version to the exported packages of org.apache.commons.logging_1.1.1.jar Regards,

          People

          • Assignee:
            Unassigned
            Reporter:
            Super Nounouille
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development