Yannick BEAUCE created DIRSTUDIO-855:
----------------------------------------
Summary: Some logical site artifact paths do not exist in site.xml
/ Apache Directory Studio 2.X Update Site / Nexus P2 Update Site Proxy
Key: DIRSTUDIO-855
URL: https://issues.apache.org/jira/browse/DIRSTUDIO-855
Project: Directory Studio
Issue Type: Bug
Components: studio-updatesite
Affects Versions: 2.0.0
Reporter: Yannick BEAUCE
Priority: Minor
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" ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
