[
https://issues.jboss.org/browse/JBIDE-20747?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-20747:
----------------------------------------
[~dgolovin]: Installation-tests using install-grinder are testing the p2 consistency of
our target-platform, main update-site and Central. It doesn't check that things work
well after installation, it just checks that things are installed. What it does and check
is partly documented on the job page.
This kind of issue is made possible because p2 does not support the "capability"
definition while resolving dependencies (
https://dev.eclipse.org/mhonarc/lists/p2-dev/msg05417.html ), so it can for example
install org.eclipse.jetty.websocket.servlet without installing the bundle providing the
necessary capability. Then loading jetty.websocket fails at runtime, and by consequence,
everything that depends on it fails to load.
[~ldimaggio] You tried against current 4.3.1/9.1.0, right? This failure is about master
install-grinder returns a blue ball but fails to install 5 plugins
due to missing capability &/or package
---------------------------------------------------------------------------------------------------------
Key: JBIDE-20747
URL:
https://issues.jboss.org/browse/JBIDE-20747
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.4.0.Alpha1
Reporter: Nick Boldt
Assignee: Mickael Istria
Priority: Critical
Fix For: 4.4.0.Alpha1
Attachments: features.txt, plugins.txt
This happened in
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
{code}
org.osgi.framework.BundleException: Could not resolve module:
org.jboss.tools.browsersim.eclipse [1120]
Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui;
bundle-version="3.7.0"
-> Bundle-SymbolicName: org.jboss.tools.browsersim.ui;
bundle-version="3.7.0.CR1-v20150901-2111-B229"; singleton:="true"
org.jboss.tools.browsersim.ui [1122]
Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server;
bundle-version="[9.0.0,10.0.0)"
-> Bundle-SymbolicName: org.eclipse.jetty.websocket.server;
bundle-version="9.2.13.v20150730"
org.eclipse.jetty.websocket.server [555]
Unresolved requirement: Require-Capability: osgi.extender;
filter:="(osgi.extender=osgi.serviceloader.registrar)"
Unresolved requirement: Import-Package:
org.eclipse.jetty.websocket.servlet; version="[9.0.0,10.0.0)"
-> Export-Package: org.eclipse.jetty.websocket.servlet;
bundle-symbolic-name="org.eclipse.jetty.websocket.servlet";
bundle-version="9.2.13.v20150730"; version="9.2.13"
org.eclipse.jetty.websocket.servlet [556]
Unresolved requirement: Require-Capability: osgi.serviceloader;
filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)";
cardinality:="multiple"
-> Provide-Capability: osgi.serviceloader;
osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory"
{code}
--
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
Similar problems for other IUs:
{code}
org.osgi.framework.BundleException: Could not resolve module:
org.jboss.tools.cordovasim.eclipse [1163]
org.osgi.framework.BundleException: Could not resolve module:
org.jboss.tools.feedhenry.ui [1166]
org.osgi.framework.BundleException: Could not resolve module:
org.jboss.tools.livereload.core [1221]
org.osgi.framework.BundleException: Could not resolve module:
org.jboss.tools.livereload.ui [1222]
{code}
But the job was successful!
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)