Uploaded image for project: 'Directory Studio'
  1. Directory Studio
  2. DIRSTUDIO-855

Some logical site artifact paths do not exist in site.xml / Apache Directory Studio 2.X Update Site / Nexus P2 Update Site Proxy

    Details

      Description

      I've been trying to install Directory Studio LDAP Browser through a Nexus P2 Update Site proxy for Apache Directory Studio 2.x, with no luck because of required artifacts not being found during the process. I've filed a bug report with Nexus on the matter, and upon looking at Igor Fedorenko's comment on the subject (https://issues.sonatype.org/browse/NEXUS-5386?focusedCommentId=175207&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-175207), I'm wondering if there might be a problem in some of the feature.xml files included in the features jars, not referencing the correct artifact versions...

      For example, the feature jar "org.apache.directory.studio.ldapbrowser.feature_2.0.0.v20120224.jar" contains a feature.xml file referencing the org.apache.commons.codec plugin 1.6 :
      ...
      <plugin
      id="org.apache.commons.codec"
      download-size="0"
      install-size="0"
      version="1.6"
      unpack="false"/>
      ...
      But such version cannot be found in the site.xml file, as it describes this :

      ...
      <archive
      path="plugins/org.apache.commons.codec_1.6.0.jar"
      url="http://mirrors.ircam.fr/pub/apache//directory/studio/update/2.x/plugins/org.apache.commons.codec_1.6.0.jar"/>
      ...

      which isn't what is expected by Nexus because it looks for the path "plugins/org.apache.commons.codec_1.6.jar"

      Here is the list of artifacts that Nexus cannot find :

      plugins/org.apache.commons.codec_1.6.jar
      plugins/org.apache.commons.io_2.1.jar
      plugins/org.apache.commons.lang_2.6.jar
      plugins/org.bouncycastle.bcprov.jdk15_140.jar

      Is it right to mention version "1.6" in the feature.xml file when the site.xml mentions "1.6.0" ?

        Activity

        Hide
        seelmann Stefan Seelmann added a comment -

        With the next release (not scheduled yet) we will publish a P2 repository. The issue with different Maven and OSGi version scheme has been fixed.

        Show
        seelmann Stefan Seelmann added a comment - With the next release (not scheduled yet) we will publish a P2 repository. The issue with different Maven and OSGi version scheme has been fixed.
        Hide
        pamarcelot Pierre-Arnaud Marcelot added a comment -

        Indeed, there is a small problem here.
        Hopefully Eclipse handles it pretty well.

        This problem occurs with version number that not following the X.Y.Z standard (not having a Z and sometimes even a Y component).

        I will try to have this fixed for the next release.

        Show
        pamarcelot Pierre-Arnaud Marcelot added a comment - Indeed, there is a small problem here. Hopefully Eclipse handles it pretty well. This problem occurs with version number that not following the X.Y.Z standard (not having a Z and sometimes even a Y component). I will try to have this fixed for the next release.

          People

          • Assignee:
            seelmann Stefan Seelmann
            Reporter:
            yba Yannick BEAUCE
          • Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development