Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Director: Cannot resolve (existing) dependency
Director: Cannot resolve (existing) dependency [message #1752643] Wed, 25 January 2017 17:30
Timofei Sablin is currently offline Timofei SablinFriend
Messages: 1
Registered: January 2017
Junior Member
Hello all,
I'm building a full KNIME for Linux from the baseline, by running standalone p2/director on Linux to install IU's. Here is the error output that I get:

Installing 3.3.0.v201611220757.
Installing org.knime.product.desktop 3.3.1.v201612192115.
Installing 3.3.1.v201612192115.
Installing 0.2.200.v201602081511.
Installing 3.2.2.v201612161513.
Installing 1.6.100.v201610311549.
Installing 3.3.1.v201612192115.
Installing 3.2.2.v201612161518.
Installation failed.
Cannot complete the install because one or more required items could not be found.
 Software being installed: Eclipse BIRT Report Designer XML Tab Editor 4.6.0.v201606072122 ( 4.6.0.v201606072122)
 Missing requirement: XML Schema Editor 1.2.600.v201511240159 (org.eclipse.wst.xsd.ui 1.2.600.v201511240159) requires '[sgi.bundle org.eclipse.wst.sse.ui [1.2.0,1.4.0)' but it could not be found
 Cannot satisfy dependency:
  From: Eclipse BIRT Report Designer XML Tab Editor 4.6.0.v201606072122 ( 4.6.0.v201606072122)
  To: 3.0.0
 Cannot satisfy dependency:
  From: Eclipse XML Editors and Tools 3.8.0.v201608061842 ( 3.8.0.v201608061842)
  To: org.eclipse.wst.xsd.ui [1.2.600.v201511240159]
Application failed, log file location: /apps/knime/buildtools/director/configuration/1485362367415.log

Interestingly, the bundle
is in /plugins and it's version is 1.3.600. It's also present in the artifacts.xml which is in the root of the mirror.

Here is the original command line arguments to director:

Command-line arguments:  -repository file://,file://,file:///apps/knime/workspace/knime3.x-dev-build-nodes/buckminster.output/fdknime.update_3.1.0-eclipse.feature/site.p2 -installIU <bunch of comma separated IU's> -destination /apps/knime/workspace/knime3.x-dev-execute-tests/knimeTestInstance_new -profile KNIMEProfile -profileProperties org.eclipse.update.install.features=true -bundlepool /apps/knime/workspace/knime3.x-dev-execute-tests/knimeTestInstance_new -p2.os linux - gtk -p2.arch x86_64 -roaming

Some facts:
* The build machine is the same as where the mirror is, so I tried using file:/// to access the mirror.
* The problem occurred when we switched from old Ant mirroring, to a more modern and simple mirroring:

mirror () {

echo Mirroring metadata for $2
java -jar $1/plugins/org.eclipse.equinox.launcher_*.jar \
     -application org.eclipse.equinox.p2.metadata.repository.mirrorApplication \
     -source $2 \
     -destination $3 \
     -destinationName $4 \

echo Mirroring artifacts for $2
java -jar $1/plugins/org.eclipse.equinox.launcher_*.jar \
     -application org.eclipse.equinox.p2.artifact.repository.mirrorApplication \
     -source $2 \
     -destination $3 \
     -destinationName $4 \

return 0

... which basically queries external repositories and appends to the update site.

What could be the reason for such behavior? Could it be that the mirror repository format is not understood by director?

Would appreciate any help!

-Timofei Sablin

[Updated on: Sun, 29 January 2017 17:24]

Report message to a moderator

Previous Topic:site.xml - controlling "feature url" attribute in a headless build
Next Topic:plugin load from dropins folder suddenly stopped working
Goto Forum:

Current Time: Tue Mar 20 12:03:37 GMT 2018

Powered by FUDForum. Page generated in 0.01628 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software