[JBoss JIRA] (JBIDE-23422) Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-23422:
--------------------------------
Environment:
windows 10
Fedora 24
> Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.4.2.Final
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBIDE-23422) Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Ilya Buziuk (JIRA)
Ilya Buziuk created JBIDE-23422:
-----------------------------------
Summary: Node.js debug session is terminated after ~1 minute and browser shows 502 error
Key: JBIDE-23422
URL: https://issues.jboss.org/browse/JBIDE-23422
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: javascript, openshift
Affects Versions: 4.4.2.AM2
Reporter: Ilya Buziuk
Assignee: Ilya Buziuk
Fix For: 4.4.2.Final
We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBIDE-23421) Terminating Server Adapter running in debug mode does not terminate Node.js debug session
by Ilya Buziuk (JIRA)
Ilya Buziuk created JBIDE-23421:
-----------------------------------
Summary: Terminating Server Adapter running in debug mode does not terminate Node.js debug session
Key: JBIDE-23421
URL: https://issues.jboss.org/browse/JBIDE-23421
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: javascript, openshift
Affects Versions: 4.4.2.AM2
Reporter: Ilya Buziuk
Assignee: Ilya Buziuk
Fix For: 4.4.2.Final
Stopping server adapter will not stop the V8 debug session - one should still terminate it manually. This might be coupled with the replication controller issue - https://issues.jboss.org/browse/JBIDE-23412 due to the fact that after stopping server adapter app is still running in the DEV_MODE (which is unexpected behaviour IMO) and debug session is still alive. Moreover, If you try to restart the adapter the debug session will be terminated (expected behaviour), so it might be just a side effect of other issue
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4136) Uses constraint violation - org.slf4j.api vs. slf4j.api
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4136?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4136 at 10/27/16 11:20 AM:
-------------------------------------------------------------
PRs to update to use m2e 1.7.1.20161026-1743, m2e-wtp 1.3.2.20161026-1738, m2e-apt 1.3.0.201610261805 in both 4.60.x and 4.61.x branches for jbosstools and devstudio TPs:
https://github.com/jbosstools/jbosstools-target-platforms/pull/239
https://github.com/jbosstools/jbosstools-target-platforms/pull/240
P2diffs:
[^jbt4602AM1.p2diff.txt] & [^ds4610AM1.p2diff.txt]
was (Author: nickboldt):
PRs to update to use m2e 1.7.1.20161026-1743, m2e-wtp 1.3.2.20161026-1738, m2e-apt 1.3.0.201610261805 in both 4.60.x and 4.61.x branches for jbosstools and devstudio TPs:
https://github.com/jbosstools/jbosstools-target-platforms/pull/239
https://github.com/jbosstools/jbosstools-target-platforms/pull/240
> Uses constraint violation - org.slf4j.api vs. slf4j.api
> -------------------------------------------------------
>
> Key: JBDS-4136
> URL: https://issues.jboss.org/browse/JBDS-4136
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, maven, rpm, target-platform
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: ds4610AM1.p2diff.txt, enabled-sites-wtp-update.png, jbt4602AM1.p2diff.txt
>
>
> Latest bit of rpm madness...
> This conflict occurred:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jpa [931]
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"] because it is exposed to package 'org.slf4j' from resources org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"] and slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"] via two dependency chains.
> Chain 1:
> org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"]
> require: (osgi.wiring.bundle=org.slf4j.api)
> |
> provide: osgi.wiring.bundle: org.slf4j.api
> org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"]
> Chain 2:
> org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"]
> require: (osgi.wiring.bundle=org.slf4j.api)
> |
> provide: osgi.wiring.bundle; bundle-version:Version="1.7.2.v20121108-1250"; osgi.wiring.bundle="org.slf4j.api"
> org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"]
> require: (&(osgi.wiring.bundle=ch.qos.logback.classic)(&(bundle-version>=1.0.7)(!(bundle-version>=1.0.8))))
> |
> provide: osgi.wiring.bundle; bundle-version:Version="1.0.7.v20121108-1250"; osgi.wiring.bundle="ch.qos.logback.classic"
> ch.qos.logback.classic [osgi.identity; type="osgi.bundle"; version:Version="1.0.7.v20121108-1250"; osgi.identity="ch.qos.logback.classic"]
> import: (&(osgi.wiring.package=org.slf4j)(version>=1.7.0))
> |
> export: osgi.wiring.package: org.slf4j
> slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"]
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
> 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}
> So, since slf4j.api is installed via 5 upstream projects (5 symlinks, actually, to rh-java-common):
> {code}
> $➔ find . -name "*slf4j.api*jar" -exec ls -l {} \;
> lrwxrwxrwx 1 root root 81 Oct 11 13:00 ./share/eclipse/droplets/jgit/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 81 Oct 12 05:19 ./share/eclipse/droplets/linuxtools-docker/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 81 Oct 11 14:46 ./share/eclipse/droplets/egit-egit/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 75 Oct 21 09:58 ./share/eclipse/droplets/mylyn-versions-git/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/api.jar
> lrwxrwxrwx 1 root root 81 Oct 11 14:46 ./share/eclipse/droplets/egit-mylyn/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> {code}
> ... I removed it from the RPM in favour of the other bundle, which was already installed into the fedora/rhel eclipse.
> BUT... since this RH SCL rh-java-common *slf4j-api.jar* exports a different, incompatible bundle name:
> {code}Bundle-SymbolicName: slf4j.api{code}
> than the one in devstudio's update site / target platform
> {code}Bundle-SymbolicName: org.slf4j.api{code}
> NOW, I'm getting this:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jpa [931]
> Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.6.2"
> {code}
> Snjezana got this too in m2e.core:
> {code}BundleException: Could not resolve module: org.eclipse.m2e.core.ui [866]
> Unresolved requirement: Require-Bundle: org.eclipse.m2e.maven.runtime; bundle-version="[1.7.0,1.8.0)"
> -> Bundle-SymbolicName: org.eclipse.m2e.maven.runtime; bundle-version="1.7.0.20160603-1931"; singleton:="false"
> org.eclipse.m2e.maven.runtime [876]
> Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.6.2"{code}
> So... not sure what to do to solve this. :(
> I suppose the best case would be for the m2e and w2e-wtp bundles to depend on the slf4j.api PACKAGES instead of BUNDLES, so that they can run on the fedora/rhel versions instead of those from the devstudio update site / target platform.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4136) Uses constraint violation - org.slf4j.api vs. slf4j.api
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4136?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4136:
-----------------------------
Attachment: ds4610AM1.p2diff.txt
> Uses constraint violation - org.slf4j.api vs. slf4j.api
> -------------------------------------------------------
>
> Key: JBDS-4136
> URL: https://issues.jboss.org/browse/JBDS-4136
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, maven, rpm, target-platform
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: ds4610AM1.p2diff.txt, enabled-sites-wtp-update.png, jbt4602AM1.p2diff.txt
>
>
> Latest bit of rpm madness...
> This conflict occurred:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jpa [931]
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"] because it is exposed to package 'org.slf4j' from resources org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"] and slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"] via two dependency chains.
> Chain 1:
> org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"]
> require: (osgi.wiring.bundle=org.slf4j.api)
> |
> provide: osgi.wiring.bundle: org.slf4j.api
> org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"]
> Chain 2:
> org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"]
> require: (osgi.wiring.bundle=org.slf4j.api)
> |
> provide: osgi.wiring.bundle; bundle-version:Version="1.7.2.v20121108-1250"; osgi.wiring.bundle="org.slf4j.api"
> org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"]
> require: (&(osgi.wiring.bundle=ch.qos.logback.classic)(&(bundle-version>=1.0.7)(!(bundle-version>=1.0.8))))
> |
> provide: osgi.wiring.bundle; bundle-version:Version="1.0.7.v20121108-1250"; osgi.wiring.bundle="ch.qos.logback.classic"
> ch.qos.logback.classic [osgi.identity; type="osgi.bundle"; version:Version="1.0.7.v20121108-1250"; osgi.identity="ch.qos.logback.classic"]
> import: (&(osgi.wiring.package=org.slf4j)(version>=1.7.0))
> |
> export: osgi.wiring.package: org.slf4j
> slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"]
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
> 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}
> So, since slf4j.api is installed via 5 upstream projects (5 symlinks, actually, to rh-java-common):
> {code}
> $➔ find . -name "*slf4j.api*jar" -exec ls -l {} \;
> lrwxrwxrwx 1 root root 81 Oct 11 13:00 ./share/eclipse/droplets/jgit/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 81 Oct 12 05:19 ./share/eclipse/droplets/linuxtools-docker/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 81 Oct 11 14:46 ./share/eclipse/droplets/egit-egit/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 75 Oct 21 09:58 ./share/eclipse/droplets/mylyn-versions-git/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/api.jar
> lrwxrwxrwx 1 root root 81 Oct 11 14:46 ./share/eclipse/droplets/egit-mylyn/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> {code}
> ... I removed it from the RPM in favour of the other bundle, which was already installed into the fedora/rhel eclipse.
> BUT... since this RH SCL rh-java-common *slf4j-api.jar* exports a different, incompatible bundle name:
> {code}Bundle-SymbolicName: slf4j.api{code}
> than the one in devstudio's update site / target platform
> {code}Bundle-SymbolicName: org.slf4j.api{code}
> NOW, I'm getting this:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jpa [931]
> Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.6.2"
> {code}
> Snjezana got this too in m2e.core:
> {code}BundleException: Could not resolve module: org.eclipse.m2e.core.ui [866]
> Unresolved requirement: Require-Bundle: org.eclipse.m2e.maven.runtime; bundle-version="[1.7.0,1.8.0)"
> -> Bundle-SymbolicName: org.eclipse.m2e.maven.runtime; bundle-version="1.7.0.20160603-1931"; singleton:="false"
> org.eclipse.m2e.maven.runtime [876]
> Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.6.2"{code}
> So... not sure what to do to solve this. :(
> I suppose the best case would be for the m2e and w2e-wtp bundles to depend on the slf4j.api PACKAGES instead of BUNDLES, so that they can run on the fedora/rhel versions instead of those from the devstudio update site / target platform.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4136) Uses constraint violation - org.slf4j.api vs. slf4j.api
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4136?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4136:
-----------------------------
Attachment: jbt4602AM1.p2diff.txt
> Uses constraint violation - org.slf4j.api vs. slf4j.api
> -------------------------------------------------------
>
> Key: JBDS-4136
> URL: https://issues.jboss.org/browse/JBDS-4136
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, maven, rpm, target-platform
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: enabled-sites-wtp-update.png, jbt4602AM1.p2diff.txt
>
>
> Latest bit of rpm madness...
> This conflict occurred:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jpa [931]
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"] because it is exposed to package 'org.slf4j' from resources org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"] and slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"] via two dependency chains.
> Chain 1:
> org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"]
> require: (osgi.wiring.bundle=org.slf4j.api)
> |
> provide: osgi.wiring.bundle: org.slf4j.api
> org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"]
> Chain 2:
> org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"]
> require: (osgi.wiring.bundle=org.slf4j.api)
> |
> provide: osgi.wiring.bundle; bundle-version:Version="1.7.2.v20121108-1250"; osgi.wiring.bundle="org.slf4j.api"
> org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"]
> require: (&(osgi.wiring.bundle=ch.qos.logback.classic)(&(bundle-version>=1.0.7)(!(bundle-version>=1.0.8))))
> |
> provide: osgi.wiring.bundle; bundle-version:Version="1.0.7.v20121108-1250"; osgi.wiring.bundle="ch.qos.logback.classic"
> ch.qos.logback.classic [osgi.identity; type="osgi.bundle"; version:Version="1.0.7.v20121108-1250"; osgi.identity="ch.qos.logback.classic"]
> import: (&(osgi.wiring.package=org.slf4j)(version>=1.7.0))
> |
> export: osgi.wiring.package: org.slf4j
> slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"]
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
> 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}
> So, since slf4j.api is installed via 5 upstream projects (5 symlinks, actually, to rh-java-common):
> {code}
> $➔ find . -name "*slf4j.api*jar" -exec ls -l {} \;
> lrwxrwxrwx 1 root root 81 Oct 11 13:00 ./share/eclipse/droplets/jgit/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 81 Oct 12 05:19 ./share/eclipse/droplets/linuxtools-docker/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 81 Oct 11 14:46 ./share/eclipse/droplets/egit-egit/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 75 Oct 21 09:58 ./share/eclipse/droplets/mylyn-versions-git/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/api.jar
> lrwxrwxrwx 1 root root 81 Oct 11 14:46 ./share/eclipse/droplets/egit-mylyn/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> {code}
> ... I removed it from the RPM in favour of the other bundle, which was already installed into the fedora/rhel eclipse.
> BUT... since this RH SCL rh-java-common *slf4j-api.jar* exports a different, incompatible bundle name:
> {code}Bundle-SymbolicName: slf4j.api{code}
> than the one in devstudio's update site / target platform
> {code}Bundle-SymbolicName: org.slf4j.api{code}
> NOW, I'm getting this:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jpa [931]
> Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.6.2"
> {code}
> Snjezana got this too in m2e.core:
> {code}BundleException: Could not resolve module: org.eclipse.m2e.core.ui [866]
> Unresolved requirement: Require-Bundle: org.eclipse.m2e.maven.runtime; bundle-version="[1.7.0,1.8.0)"
> -> Bundle-SymbolicName: org.eclipse.m2e.maven.runtime; bundle-version="1.7.0.20160603-1931"; singleton:="false"
> org.eclipse.m2e.maven.runtime [876]
> Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.6.2"{code}
> So... not sure what to do to solve this. :(
> I suppose the best case would be for the m2e and w2e-wtp bundles to depend on the slf4j.api PACKAGES instead of BUNDLES, so that they can run on the fedora/rhel versions instead of those from the devstudio update site / target platform.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4137) JS editor fails to open
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBDS-4137?page=com.atlassian.jira.plugin.... ]
Ilya Buziuk edited comment on JBDS-4137 at 10/27/16 10:47 AM:
--------------------------------------------------------------
[~akazakov] no comments - info provided in the issue's description is correct and informative
[~nickboldt] weird that it works for you without a hook though
was (Author: ibuziuk):
[~akazakov] no comments - info provided in the issue's description is correct and informative
[~nickboldt] weird that it worls for you without a hook though
> JS editor fails to open
> -----------------------
>
> Key: JBDS-4137
> URL: https://issues.jboss.org/browse/JBDS-4137
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: javascript, rpm, upstream
> Affects Versions: 10.2.0.AM2
> Reporter: Alexey Kazakov
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: js-editor-works.png
>
>
> JavaScript Editor is not working OOTB in Eclipse/devstudio installed via RPM. It fails because of missing JSDT/Equinox hook for Nashorn in eclipse.ini. See https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn
> The same error occurs if JSDT installed to an existing Eclipse via p2. So it's rather an upstream issue.
> The following line added to eclipse.ini fixes the problem:
> {code}-Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension{code}
> It works OOTB in devstudio installed via our installer because we have this hook in devstudio.ini
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4137) JS editor fails to open
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBDS-4137?page=com.atlassian.jira.plugin.... ]
Ilya Buziuk commented on JBDS-4137:
-----------------------------------
[~akazakov] no comments - info provided in the issue's description is correct and informative
[~nickboldt] weird that it worls for you without a hook though
> JS editor fails to open
> -----------------------
>
> Key: JBDS-4137
> URL: https://issues.jboss.org/browse/JBDS-4137
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: javascript, rpm, upstream
> Affects Versions: 10.2.0.AM2
> Reporter: Alexey Kazakov
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: js-editor-works.png
>
>
> JavaScript Editor is not working OOTB in Eclipse/devstudio installed via RPM. It fails because of missing JSDT/Equinox hook for Nashorn in eclipse.ini. See https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn
> The same error occurs if JSDT installed to an existing Eclipse via p2. So it's rather an upstream issue.
> The following line added to eclipse.ini fixes the problem:
> {code}-Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension{code}
> It works OOTB in devstudio installed via our installer because we have this hook in devstudio.ini
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBTIS-967) Update web pages for Devstudio IS 10.0.0.CR1
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-967:
---------------------------------------
Summary: Update web pages for Devstudio IS 10.0.0.CR1
Key: JBTIS-967
URL: https://issues.jboss.org/browse/JBTIS-967
Project: JBoss Tools Integration Stack
Issue Type: Task
Affects Versions: 10.0.0.CR1
Reporter: Andrej Podhradsky
Attachments: rhdsis-10.0.0.CR1.png
Update the following things
- update "9.x" to "10.x"
- update links to zip files
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4137) JS editor fails to open
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4137?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4137:
--------------------------------------
No, m2e is not related to JSDT. Are you sure you don't have -Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension in your eclipse.ini?
[~ibuziuk] any comments?
> JS editor fails to open
> -----------------------
>
> Key: JBDS-4137
> URL: https://issues.jboss.org/browse/JBDS-4137
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: javascript, rpm, upstream
> Affects Versions: 10.2.0.AM2
> Reporter: Alexey Kazakov
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: js-editor-works.png
>
>
> JavaScript Editor is not working OOTB in Eclipse/devstudio installed via RPM. It fails because of missing JSDT/Equinox hook for Nashorn in eclipse.ini. See https://wiki.eclipse.org/JSDT/Equinox_hook_for_Nashorn
> The same error occurs if JSDT installed to an existing Eclipse via p2. So it's rather an upstream issue.
> The following line added to eclipse.ini fixes the problem:
> {code}-Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension{code}
> It works OOTB in devstudio installed via our installer because we have this hook in devstudio.ini
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months