[JBoss JIRA] (JBIDE-25974) CDK 3.4 runtime detection failing
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25974?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25974:
---------------------------------------
I followed exactly the steps to reproduce, and since I kept my download folder default (/tmp) I encounter JBIDE-25968. So that why it just ended up with the error dialog. After changing to different directory I had no problem with downloading cdk-3.4.0.
> CDK 3.4 runtime detection failing
> ---------------------------------
>
> Key: JBIDE-25974
> URL: https://issues.jboss.org/browse/JBIDE-25974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM1
>
> Attachments: image-2018-05-07-17-59-59-316.png
>
>
> Runtime detection doesn't work for 3.4.0 with the whitelist. A regex would be better
> steps:
> # EXE: Preferences > JBoss Runtime Detection > Download
> # ASSERT: List of available runtimes shows up, containing CDK 3.4.0
> # EXEC: Choose "CDK 3.4.0" & hit "Next"
> # EXEC: next page: provide credentials & hit "Next"
> # EXEC: next page: accept the terms & hit "Next"
> # EXEC: next page: use the suggested defaults, make sure that "Install folder" is a separate folder (ex. freshly created ~/cdk/) & hit "Finish"
> # ASSERT: wait for the download to finish
> Result:
> The download wont detect the new CDK 3.4.0 that you just downloaded
> !image-2018-05-07-17-59-59-316.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25974) CDK 3.4 runtime detection failing
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25974?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-25974:
-------------------------------------
I'm not able to replicate this.
> CDK 3.4 runtime detection failing
> ---------------------------------
>
> Key: JBIDE-25974
> URL: https://issues.jboss.org/browse/JBIDE-25974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM1
>
> Attachments: image-2018-05-07-17-59-59-316.png
>
>
> Runtime detection doesn't work for 3.4.0 with the whitelist. A regex would be better
> steps:
> # EXE: Preferences > JBoss Runtime Detection > Download
> # ASSERT: List of available runtimes shows up, containing CDK 3.4.0
> # EXEC: Choose "CDK 3.4.0" & hit "Next"
> # EXEC: next page: provide credentials & hit "Next"
> # EXEC: next page: accept the terms & hit "Next"
> # EXEC: next page: use the suggested defaults, make sure that "Install folder" is a separate folder (ex. freshly created ~/cdk/) & hit "Finish"
> # ASSERT: wait for the download to finish
> Result:
> The download wont detect the new CDK 3.4.0 that you just downloaded
> !image-2018-05-07-17-59-59-316.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25974) CDK 3.4 runtime detection failing
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25974?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-25974:
--------------------------------
Fix Version/s: 4.6.0.AM1
(was: 4.6.x)
> CDK 3.4 runtime detection failing
> ---------------------------------
>
> Key: JBIDE-25974
> URL: https://issues.jboss.org/browse/JBIDE-25974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM1
>
> Attachments: image-2018-05-07-17-59-59-316.png
>
>
> Runtime detection doesn't work for 3.4.0 with the whitelist. A regex would be better
> steps:
> # EXE: Preferences > JBoss Runtime Detection > Download
> # ASSERT: List of available runtimes shows up, containing CDK 3.4.0
> # EXEC: Choose "CDK 3.4.0" & hit "Next"
> # EXEC: next page: provide credentials & hit "Next"
> # EXEC: next page: accept the terms & hit "Next"
> # EXEC: next page: use the suggested defaults, make sure that "Install folder" is a separate folder (ex. freshly created ~/cdk/) & hit "Finish"
> # ASSERT: wait for the download to finish
> Result:
> The download wont detect the new CDK 3.4.0 that you just downloaded
> !image-2018-05-07-17-59-59-316.png!
--
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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26027?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-26027 at 5/16/18 1:35 PM:
-------------------------------------------------------------
Did some digging.
org.apache.aries.spifly.dynamic.bundle 1.0.10 supports ASM 5 and 6:
{code}
Implementation-Version: 1.0.10
Import-Package: org.objectweb.asm;version="[5,7)",org.objectweb.asm.comm
ons;version="[5,7)"{code}
So if we pull this newer bundle into JBoss Locus [0] and use that instead [1], we might be able to solve this dependency problem.
[1] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.80.x/jbo...
I've rebuild Locus here:
[0] http://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/loc...
And a new TP is building here:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
Once that's built, I can update the parent pom to use this new TP, and attempt to rebuild this PR (which worked locally):
https://github.com/jbosstools/jbosstools-livereload/pull/142
was (Author: nickboldt):
Did some digging.
org.apache.aries.spifly.dynamic.bundle 1.0.10 supports ASM 5 and 6:
{code}
Implementation-Version: 1.0.10
Import-Package: org.objectweb.asm;version="[5,7)",org.objectweb.asm.comm
ons;version="[5,7)"{code}
So if we pull this newer bundle into JBoss Locus [0] and use that instead [1], we might be able to solve this dependency problem.
[1] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.80.x/jbo...
I've rebuild Locus here:
http://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/loc...
And a new TP is building here:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
Once that's built, I can update the parent pom to use this new TP, and attempt to rebuild this PR (which worked locally):
https://github.com/jbosstools/jbosstools-livereload/pull/142
> 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-26027) Jetty FrameworkEvent ERROR for LiveReload
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26027?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-26027:
------------------------------------
Did some digging.
org.apache.aries.spifly.dynamic.bundle 1.0.10 supports ASM 5 and 6:
{code}
Implementation-Version: 1.0.10
Import-Package: org.objectweb.asm;version="[5,7)",org.objectweb.asm.comm
ons;version="[5,7)"{code}
So if we pull this newer bundle into JBoss Locus [0] and use that instead [1], we might be able to solve this dependency problem.
[1] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.80.x/jbo...
I've rebuild Locus here:
http://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/loc...
And a new TP is building here:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
Once that's built, I can update the parent pom to use this new TP, and attempt to rebuild this PR (which worked locally):
https://github.com/jbosstools/jbosstools-livereload/pull/142
> 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-25736) deprecate features from JBoss Tools with low usage / low development
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25736?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25736:
------------------------------------
People have started to notice that LiveReload was deprecated in 4.5.3 / 11.3.0:
https://developer.jboss.org/message/982646?et=watches.email.thread#982646
https://stackoverflow.com/questions/50346013/missing-livereload-server-in...
> deprecate features from JBoss Tools with low usage / low development
> --------------------------------------------------------------------
>
> Key: JBIDE-25736
> URL: https://issues.jboss.org/browse/JBIDE-25736
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim, build, cdi, forge, jsf, livereload, portal-gatein, seam2, webservices
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.Final
>
> Attachments: Screenshot 2018-03-02 14.51.03.png
>
>
> This issue is to consider *deprecating* the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked.
> * jbosstools-portlet
> * jbosstools-aerogear
> * jbosstools-browsersim
> * jbosstools-livereload
> * {color:red}-jbosstools-webservices-{color}
> * {color:red}-jbosstools-javaee-{color}
> * {color:red}-jbosstools-forge-{color}
> These projects could be *removed*, since they were deprecated some time ago:
> * jbosstools-freemarker
> * jbosstools-arquillian
> For supporting arguments, see this doc (RH only, sorry):
> https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (ERT-623) Evaluate combination of Docker images of LS (from Che?) with LSP4E
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/ERT-623?page=com.atlassian.jira.plugin.sy... ]
Mickael Istria commented on ERT-623:
------------------------------------
Another LinuxTools issue I think it critical for this workflow to be convenient: https://bugs.eclipse.org/bugs/show_bug.cgi?id=534725
> Evaluate combination of Docker images of LS (from Che?) with LSP4E
> ------------------------------------------------------------------
>
> Key: ERT-623
> URL: https://issues.jboss.org/browse/ERT-623
> Project: Eclipse Release Train
> Issue Type: Enhancement
> Reporter: Mickael Istria
>
> LSP4E offers a way to dynamically associate a Launch configuration representing a language server (communicating over stdio) with a content type to enable LS-based edition assistance in editor.
> It would be interesting to try this using a Docker Launch Configuration with LSP4E, more particularly, it'd be nice to test the Docker LS images that are created for Eclipse Che.
> cc [~rgrunber] : any obvious concern about it?
> cc [~flbe] : are the image for Language Server in Che streaming the LS messages over stdio? Or is it using another channel?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months