[JBoss JIRA] (JBIDE-26578) org.jboss.tools.openshift.ui fails to load
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26578?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26578.
---------------------------------
OpenShift UI is working under JDK8.
Verified in:
Red Hat CodeReady Studio
Version: 12.11.0.GA
Build id: GA-v20190321-1925-B4244
Build date: 20190321-1925
> org.jboss.tools.openshift.ui fails to load
> ------------------------------------------
>
> Key: JBIDE-26578
> URL: https://issues.jboss.org/browse/JBIDE-26578
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.AM1
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.11.0.Final
>
>
> The bundle fails to load with this error:
> {code:java}
> !ENTRY org.jboss.tools.openshift.ui 4 0 2019-03-18 18:56:49.104
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.openshift.ui [1088]
> Bundle was not resolved because of a uses constraint violation.
> org.apache.felix.resolver.reason.ReasonException: Uses constraint violation. Unable to resolve resource org.jboss.tools.openshift.ui [osgi.identity; type="osgi.bundle"; version:Version="3.6.0.v20190220-1733"; osgi.identity="org.jboss.tools.openshift.ui"; singleton:="true"] because it is exposed to package 'javax.xml.bind.annotation' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.13.300.v20190218-1622"; singleton:="true"] and javax.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.2.0.v201105210648"; osgi.identity="javax.xml.bind"] via two dependency chains.
> {code:java}
> Chain 1:
> org.jboss.tools.openshift.ui [osgi.identity; type="osgi.bundle"; version:Version="3.6.0.v20190220-1733"; osgi.identity="org.jboss.tools.openshift.ui"; singleton:="true"]
> require: (osgi.wiring.bundle=org.eclipse.core.runtime)
> |
> provide: osgi.wiring.bundle: org.eclipse.core.runtime
> org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.13.300.v20190218-1622"; singleton:="true"]
> Chain 2:
> org.jboss.tools.openshift.ui [osgi.identity; type="osgi.bundle"; version:Version="3.6.0.v20190220-1733"; osgi.identity="org.jboss.tools.openshift.ui"; singleton:="true"]
> require: (&(osgi.wiring.bundle=com.spotify.docker.client)(bundle-version>=3.4.0))
> |
> provide: osgi.wiring.bundle; bundle-version:Version="8.11.7.v20180731-1413"; osgi.wiring.bundle="com.spotify.docker.client"
> com.spotify.docker.client [osgi.identity; type="osgi.bundle"; version:Version="8.11.7.v20180731-1413"; osgi.identity="com.spotify.docker.client"]
> import: (&(osgi.wiring.package=javax.ws.rs)(version>=2.0.0))
> |
> export: osgi.wiring.package=javax.ws.rs; uses:=javax.xml.bind.annotation
> javax.ws.rs [osgi.identity; type="osgi.bundle"; version:Version="2.0.1.v201504171603"; osgi.identity="javax.ws.rs"]
> import: (&(osgi.wiring.package=javax.xml.bind.annotation)(&(version>=2.2.0)(!(version>=3.0.0))))
> |
> export: osgi.wiring.package: javax.xml.bind.annotation
> javax.xml.bind [osgi.identity; type="osgi.bundle"; version:Version="2.2.0.v201105210648"; osgi.identity="javax.xml.bind"]
> at org.eclipse.osgi.container.Module.start(Module.java:452)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1784)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1763)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1726)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1657)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343)
> {code}
> This does not happen with Java11. This seems to be cause because org.eclipse.osgi exports javax.xml.bind packages and the new Docker stuff is requesting a specific version of javax.xml.bind thus we have two versions of the packages.
> Solution is to replace require bundle org.eclipse.core.runtime by import package
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
[JBoss JIRA] (JBIDE-26562) debugging does not work for eap-cd-basic-s2i template from CRC
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26562?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26562.
---------------------------------
Closing. Works now.
Verified in:
Red Hat CodeReady Studio
Version: 12.11.0.GA
Build id: GA-v20190321-1925-B4244
Build date: 20190321-1925
> debugging does not work for eap-cd-basic-s2i template from CRC
> --------------------------------------------------------------
>
> Key: JBIDE-26562
> URL: https://issues.jboss.org/browse/JBIDE-26562
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift, server
> Affects Versions: 4.11.0.AM1
> Environment: F29, devstudio AM1-v20190221-1020-B4114, CDK v3.8.0-alpha.1-1
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.11.0.Final
>
> Attachments: image-2019-02-26-10-19-19-366.png, image-2019-03-14-16-30-04-450.png, image-2019-03-18-12-06-33-851.png
>
>
> Restarting server adapter in debug for openshift application results in not responding job *Enabling "openshift maven profile"*: !image-2019-02-26-10-19-19-366.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months
[JBoss JIRA] (JBIDE-26584) Central New and Noteworthy for 4.11.0.Final
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26584?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-26584.
------------------------------
Resolution: Rejected
> Central New and Noteworthy for 4.11.0.Final
> ------------------------------------------------------
>
> Key: JBIDE-26584
> URL: https://issues.jboss.org/browse/JBIDE-26584
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: task
> Fix For: 4.11.0.Final
>
>
> Jeff MAURY,
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed Central JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
> * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
> If no N&N issues are found for Central, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for Central by submitting a pull request against:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> If your PR's commit comment is of the form... {code}JBIDE-26583 #comment Create N&N for Central 4.11.0.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
> If there is nothing new or noteworthy for Central for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.11.0.Final since the AM3 release of Central, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.11.0.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.11.0.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 2 months