[JBoss JIRA] (JBIDE-20670) LiveReload, BrowserSim and CordovaSim broken after TP changes (Jetty)

Wednesday, 16 September 2015

    [
https://issues.jboss.org/browse/JBIDE-20670?page=com.atlassian.jira.plugi...
] 

Vlado Pakan commented on JBIDE-20670:
-------------------------------------

I'm getting similar errors with JBDS 9.0.0.CR1-v20150912-1100-B100 but only after I
have installed Mobile Hybrid tooling from JBoss Central. I guess it should be also fixed
with linked PR's?

{noformat}
!ENTRY org.jboss.tools.browsersim.eclipse 4 0 2015-09-16 14:31:01.529
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module:
org.jboss.tools.browsersim.eclipse [874]
  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-v20150911-0358-B25"; singleton:="true"
       org.jboss.tools.browsersim.ui [876]
         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 [1057]
                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 [1058]
                       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"

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY org.jboss.tools.livereload.core 4 0 2015-09-16 14:31:01.534
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module:
org.jboss.tools.livereload.core [958]
  Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server;
bundle-version="[9.2.10,9.3.0)"; visibility:="reexport"
    -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server;
bundle-version="9.2.13.v20150730"
       org.eclipse.jetty.websocket.server [1057]
         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 [1058]
                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"

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY org.jboss.tools.livereload.ui 4 0 2015-09-16 14:31:01.538
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module:
org.jboss.tools.livereload.ui [959]
  Unresolved requirement: Require-Bundle: org.jboss.tools.livereload.core;
bundle-version="1.0.0"
    -> Bundle-SymbolicName: org.jboss.tools.livereload.core;
bundle-version="1.3.0.CR1-v20150911-0426-B23"; singleton:="true"
       org.jboss.tools.livereload.core [958]
         Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server;
bundle-version="[9.2.10,9.3.0)"; visibility:="reexport"
           -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server;
bundle-version="9.2.13.v20150730"
              org.eclipse.jetty.websocket.server [1057]
                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 [1058]
                       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"

	at org.eclipse.osgi.container.Module.start(Module.java:434)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
	at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
{noformat}

...
 LiveReload, BrowserSim and CordovaSim broken after TP changes
(Jetty)
 ---------------------------------------------------------------------

                 Key: JBIDE-20670
                 URL: https://issues.jboss.org/browse/JBIDE-20670
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: browsersim, cordovasim, livereload, target-platform
    Affects Versions: 4.3.0.CR1
            Reporter: Xavier Coulon
            Assignee: Xavier Coulon
            Priority: Blocker
              Labels: respin-a
             Fix For: 4.3.0.CR1

 After the latest TP changes, the Jetty dependencies were set at a specific range to
exclude the latest versions of some Jetty bundles brought as transitive dependencies of
other bundles, using {{[9.2.10, 9.3)}}, but the TP itself was wrong and contained Eclipse
Neon bundles (see JBIDE-20662). After the TP was fixed, the unwanted Jetty bundles were in
version {{9.2.13}} which was caught by the specific range aforementioned, but this causes
runtime errors because some classes cannot be resolved
({{org.eclipse.jetty.util.thread.Spinlock}}, for example). 

--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006