[JBoss JIRA] (JBIDE-26027) Jetty FrameworkEvent ERROR for LiveReload
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26027?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-26027.
---------------------------------
Verified in devstudio-12.0.0.AM2-v20180523-0533-B2531-installer-standalone.jar. The error no longer shows up.
> Jetty FrameworkEvent ERROR for LiveReload
> -----------------------------------------
>
> Key: JBIDE-26027
> URL: https://issues.jboss.org/browse/JBIDE-26027
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload, upstream
> Affects Versions: 4.6.0.AM1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM2
>
>
> When you install LiveReload from Central in devstudio 12.0.0.AM2, there are two errors due to incompatible version of Jetty:
> {code}
> FrameworkEvent ERROR
> {code}
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1082]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.servlet; bundle-version="[9.4.0,9.5.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.servlet; bundle-version="9.4.8.v20171121"
> org.eclipse.jetty.websocket.servlet [1081]
> 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"
> org.eclipse.jetty.websocket.server [1080]
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.4.8,9.4.9)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.4.8.v20171121"; version="9.4.8"
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> -> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.registrar"; version:Version="1.0.0"
> org.apache.aries.spifly.dynamic.bundle [1073]
> No resolution report for the bundle. Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.processor)"
> -> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.processor"; version:Version="1.0.0"
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.4.0,9.5.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.4.8.v20171121"
> Unresolved requirement: Require-Bundle: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
> -> Bundle-SymbolicName: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"] because it is exposed to package 'org.objectweb.asm' from resources org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"] and org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"] via two dependency chains.
> Chain 1:
> org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
> import: (&(osgi.wiring.package=org.objectweb.asm)(&(version>=5.0.0)(!(version>=6.0.0))))
> |
> export: osgi.wiring.package: org.objectweb.asm
> org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"]
> Chain 2:
> org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
> import: (&(osgi.wiring.package=org.objectweb.asm.commons)(&(version>=5.0.0)(!(version>=6.0.0))))
> |
> export: osgi.wiring.package=org.objectweb.asm.commons; uses:=org.objectweb.asm
> org.objectweb.asm.commons [osgi.identity; osgi.identity="org.objectweb.asm.commons"; type="osgi.bundle"; version:Version="5.0.1.v201404251740"]
> import: (osgi.wiring.package=org.objectweb.asm)
> |
> export: osgi.wiring.package: org.objectweb.asm
> org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"]
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1682)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1661)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1624)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1555)
> 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)
> {code}
> {code}
> FrameworkEvent ERROR
> {code}
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1083]
> Unresolved requirement: Require-Bundle: org.jboss.tools.livereload.core; bundle-version="1.0.0"
> -> Bundle-SymbolicName: org.jboss.tools.livereload.core; bundle-version="1.5.1.v20170822-1705"; singleton:="true"
> org.jboss.tools.livereload.core [1082]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.servlet; bundle-version="[9.4.0,9.5.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.servlet; bundle-version="9.4.8.v20171121"
> org.eclipse.jetty.websocket.servlet [1081]
> 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"
> org.eclipse.jetty.websocket.server [1080]
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.4.8,9.4.9)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.4.8.v20171121"; version="9.4.8"
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> -> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.registrar"; version:Version="1.0.0"
> org.apache.aries.spifly.dynamic.bundle [1073]
> No resolution report for the bundle. Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.processor)"
> -> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.processor"; version:Version="1.0.0"
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.4.0,9.5.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.4.8.v20171121"
> Unresolved requirement: Require-Bundle: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
> -> Bundle-SymbolicName: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"] because it is exposed to package 'org.objectweb.asm' from resources org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"] and org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"] via two dependency chains.
> Chain 1:
> org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
> import: (&(osgi.wiring.package=org.objectweb.asm)(&(version>=5.0.0)(!(version>=6.0.0))))
> |
> export: osgi.wiring.package: org.objectweb.asm
> org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"]
> Chain 2:
> org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
> import: (&(osgi.wiring.package=org.objectweb.asm.commons)(&(version>=5.0.0)(!(version>=6.0.0))))
> |
> export: osgi.wiring.package=org.objectweb.asm.commons; uses:=org.objectweb.asm
> org.objectweb.asm.commons [osgi.identity; osgi.identity="org.objectweb.asm.commons"; type="osgi.bundle"; version:Version="5.0.1.v201404251740"]
> import: (osgi.wiring.package=org.objectweb.asm)
> |
> export: osgi.wiring.package: org.objectweb.asm
> org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"]
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1682)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1661)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1624)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1555)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-25923:
---------------------------------------
[~arnieAustin], do you have steps to reproduce this? I tried starting wildfly 12 after unzipping and it worked fine for me.
[~odockal], can you confirm if it's still happening for you? I was unable to reproduce.
> Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-25923
> URL: https://issues.jboss.org/browse/JBIDE-25923
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.3.Final
> Environment: Fedora, JBoss EAP 7.1, WildFly 11, 12
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.6.0.AM1
>
> Attachments: ServerAdapterEAP.gif, ServerAdapterEAPRepaired.gif
>
>
> When there is specific maven project imported in Project explorer (jbosstools-openshift), Started EAP 7.1 server adapter is printing output where deployment scanner replaces deployment and redeploy over and over again, see part of log:
> {code}
> 15:35:15,824 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml")
> 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml")
> 15:35:20,856 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml")
> 15:35:25,951 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 20ms
> 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "standalone.v3.xml" (runtime-name: "standalone.v3.xml")
> 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:35:25,957 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 2ms
> 15:35:25,964 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:35:26,037 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
> 15:35:26,038 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v3.xml" (runtime-name : "standalone.v3.xml")
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26027) Jetty FrameworkEvent ERROR for LiveReload
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26027?page=com.atlassian.jira.plugi... ]
Jeff MAURY resolved JBIDE-26027.
--------------------------------
Resolution: Done
> Jetty FrameworkEvent ERROR for LiveReload
> -----------------------------------------
>
> Key: JBIDE-26027
> URL: https://issues.jboss.org/browse/JBIDE-26027
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload, upstream
> Affects Versions: 4.6.0.AM1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM2
>
>
> When you install LiveReload from Central in devstudio 12.0.0.AM2, there are two errors due to incompatible version of Jetty:
> {code}
> FrameworkEvent ERROR
> {code}
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1082]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.servlet; bundle-version="[9.4.0,9.5.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.servlet; bundle-version="9.4.8.v20171121"
> org.eclipse.jetty.websocket.servlet [1081]
> 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"
> org.eclipse.jetty.websocket.server [1080]
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.4.8,9.4.9)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.4.8.v20171121"; version="9.4.8"
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> -> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.registrar"; version:Version="1.0.0"
> org.apache.aries.spifly.dynamic.bundle [1073]
> No resolution report for the bundle. Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.processor)"
> -> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.processor"; version:Version="1.0.0"
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.4.0,9.5.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.4.8.v20171121"
> Unresolved requirement: Require-Bundle: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
> -> Bundle-SymbolicName: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"] because it is exposed to package 'org.objectweb.asm' from resources org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"] and org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"] via two dependency chains.
> Chain 1:
> org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
> import: (&(osgi.wiring.package=org.objectweb.asm)(&(version>=5.0.0)(!(version>=6.0.0))))
> |
> export: osgi.wiring.package: org.objectweb.asm
> org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"]
> Chain 2:
> org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
> import: (&(osgi.wiring.package=org.objectweb.asm.commons)(&(version>=5.0.0)(!(version>=6.0.0))))
> |
> export: osgi.wiring.package=org.objectweb.asm.commons; uses:=org.objectweb.asm
> org.objectweb.asm.commons [osgi.identity; osgi.identity="org.objectweb.asm.commons"; type="osgi.bundle"; version:Version="5.0.1.v201404251740"]
> import: (osgi.wiring.package=org.objectweb.asm)
> |
> export: osgi.wiring.package: org.objectweb.asm
> org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"]
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1682)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1661)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1624)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1555)
> 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)
> {code}
> {code}
> FrameworkEvent ERROR
> {code}
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1083]
> Unresolved requirement: Require-Bundle: org.jboss.tools.livereload.core; bundle-version="1.0.0"
> -> Bundle-SymbolicName: org.jboss.tools.livereload.core; bundle-version="1.5.1.v20170822-1705"; singleton:="true"
> org.jboss.tools.livereload.core [1082]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.servlet; bundle-version="[9.4.0,9.5.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.servlet; bundle-version="9.4.8.v20171121"
> org.eclipse.jetty.websocket.servlet [1081]
> 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"
> org.eclipse.jetty.websocket.server [1080]
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.4.8,9.4.9)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.4.8.v20171121"; version="9.4.8"
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> -> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.registrar"; version:Version="1.0.0"
> org.apache.aries.spifly.dynamic.bundle [1073]
> No resolution report for the bundle. Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.processor)"
> -> Provide-Capability: osgi.extender; osgi.extender="osgi.serviceloader.processor"; version:Version="1.0.0"
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.4.0,9.5.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.4.8.v20171121"
> Unresolved requirement: Require-Bundle: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
> -> Bundle-SymbolicName: org.apache.aries.spifly.dynamic.bundle; bundle-version="1.0.2"
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"] because it is exposed to package 'org.objectweb.asm' from resources org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"] and org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"] via two dependency chains.
> Chain 1:
> org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
> import: (&(osgi.wiring.package=org.objectweb.asm)(&(version>=5.0.0)(!(version>=6.0.0))))
> |
> export: osgi.wiring.package: org.objectweb.asm
> org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="5.0.1.v201404251740"; osgi.identity="org.objectweb.asm"]
> Chain 2:
> org.apache.aries.spifly.dynamic.bundle [osgi.identity; osgi.identity="org.apache.aries.spifly.dynamic.bundle"; type="osgi.bundle"; version:Version="1.0.2"]
> import: (&(osgi.wiring.package=org.objectweb.asm.commons)(&(version>=5.0.0)(!(version>=6.0.0))))
> |
> export: osgi.wiring.package=org.objectweb.asm.commons; uses:=org.objectweb.asm
> org.objectweb.asm.commons [osgi.identity; osgi.identity="org.objectweb.asm.commons"; type="osgi.bundle"; version:Version="5.0.1.v201404251740"]
> import: (osgi.wiring.package=org.objectweb.asm)
> |
> export: osgi.wiring.package: org.objectweb.asm
> org.objectweb.asm [osgi.identity; type="osgi.bundle"; version:Version="6.0.0.v20170929-1901"; osgi.identity="org.objectweb.asm"]
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1682)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1661)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1624)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1555)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25971) Add Red Hat Developers sign up link to CDK New Server wizard
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25971?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-25971.
---------------------------------
OK, fair enough. I veriried that the new registration link is there at the page shown in the screenshot in this JIRA description. Also, JBoss.org Credentials is renamed to Credentials.
> Add Red Hat Developers sign up link to CDK New Server wizard
> ------------------------------------------------------------
>
> Key: JBIDE-25971
> URL: https://issues.jboss.org/browse/JBIDE-25971
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.3.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: cdk_server_adapter_wizard
> Fix For: 4.6.0.AM2
>
> Attachments: new-server-cdk.png
>
>
> While reviewing documentation updates for cdk installation in devstudio, we noticed a thing that is not ideal in the workflow.
> Imagine you don't have an account on developers.redhat.com yet.
> You go to New Server -> CDK 3.2+.
> On the next page, you're supposed to fill out your credentials, but you don't have any. Yes, you could argue that there is a way to get there: If you don't have an account, that probably also means that you don't have a cdk binary either - you need the account to download it. So you need to click Download and install runtime... and that will offer you a link to register. So once cdk is downloaded, you can then add the credentials. But that's pretty cumbersome.
> So I would suggest we add a Register link somewhere - either on the New Server wizard's second page. Or once you click Add.. to add credentials.
> That's issue 1.
> !new-server-cdk.png!
> There are also a few side issues:
> 2. I would suggest you remove the Domain field/dropdown from the wizard. It's always just greyed out. If we ever want to support more of them we can add it back. And when you add the credentials you will see the domain there too, which is enough.
> 3. When you click Download and install runtime..., select a version and then go to the next page, this page is called JBoss.org Credentials - it's actually access.redhat.com credentials, can you change the title?
> 3.a Also, the link for signing up leads to access.redhat.com. Wouldn't it be better to point to developers.redhat.com sign up page? That's what devsuite installer does.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months