[JBoss JIRA] (JBDS-3558) Cannot install Openshift 3 tooling from central on nightly
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3558?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3558:
------------------------------
Priority: Critical (was: Major)
> Cannot install Openshift 3 tooling from central on nightly
> ----------------------------------------------------------
>
> Key: JBDS-3558
> URL: https://issues.jboss.org/browse/JBDS-3558
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, openshift
> Affects Versions: 9.0.1.Beta1
> Environment: jboss-devstudio-9.0.1.Beta1-v20151105-0411-B134-installer-standalone
> Reporter: Jan Richter
> Assignee: Max Rydahl Andersen
> Priority: Critical
>
> When I try to install Openshift 3 tooling from central on nightly 9.0.1.Beta1, it fails with this message:
> {noformat}
> Your original request has been modified.
> "JBoss Tools EGit Integration" will be ignored because a newer version is already installed.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss OpenShift 3 Tools 3.0.0.Final-v20151002-2059-B50 (org.jboss.tools.openshift.feature.feature.group 3.0.0.Final-v20151002-2059-B50)
> Software currently installed: JBoss Developer Studio (Branded Product) 9.0.1.Beta1-v20151105-0411-B134 (com.jboss.devstudio.core.package 9.0.1.Beta1-v20151105-0411-B134)
> Only one of the following can be installed at once:
> OpenShift Common UI 3.1.0.Beta1-v20151104-0336-B66 (org.jboss.tools.openshift.common.ui 3.1.0.Beta1-v20151104-0336-B66)
> OpenShift Common UI 3.0.0.Final-v20151002-2059-B50 (org.jboss.tools.openshift.common.ui 3.0.0.Final-v20151002-2059-B50)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 9.0.1.Beta1-v20151105-0411-B134 (com.jboss.devstudio.core.feature.feature.group 9.0.1.Beta1-v20151105-0411-B134)
> To: org.jboss.tools.openshift.express.feature.feature.group [3.1.0.Beta1-v20151104-0336-B66]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 9.0.1.Beta1-v20151105-0411-B134 (com.jboss.devstudio.core.package 9.0.1.Beta1-v20151105-0411-B134)
> To: com.jboss.devstudio.core.feature.feature.group [9.0.1.Beta1-v20151105-0411-B134]
> Cannot satisfy dependency:
> From: JBoss OpenShift 2 Tools 3.1.0.Beta1-v20151104-0336-B66 (org.jboss.tools.openshift.express.feature.feature.group 3.1.0.Beta1-v20151104-0336-B66)
> To: org.jboss.tools.openshift.common.ui [3.1.0.Beta1-v20151104-0336-B66]
> Cannot satisfy dependency:
> From: JBoss OpenShift 3 Tools 3.0.0.Final-v20151002-2059-B50 (org.jboss.tools.openshift.feature.feature.group 3.0.0.Final-v20151002-2059-B50)
> To: org.jboss.tools.openshift.common.ui [3.0.0.Final-v20151002-2059-B50]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3558) Cannot install Openshift 3 tooling from central on nightly
by Jan Richter (JIRA)
Jan Richter created JBDS-3558:
---------------------------------
Summary: Cannot install Openshift 3 tooling from central on nightly
Key: JBDS-3558
URL: https://issues.jboss.org/browse/JBDS-3558
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: central, openshift
Affects Versions: 9.0.1.Beta1
Environment: jboss-devstudio-9.0.1.Beta1-v20151105-0411-B134-installer-standalone
Reporter: Jan Richter
Assignee: Max Rydahl Andersen
When I try to install Openshift 3 tooling from central on nightly 9.0.1.Beta1, it fails with this message:
{noformat}
Your original request has been modified.
"JBoss Tools EGit Integration" will be ignored because a newer version is already installed.
Cannot complete the install because of a conflicting dependency.
Software being installed: JBoss OpenShift 3 Tools 3.0.0.Final-v20151002-2059-B50 (org.jboss.tools.openshift.feature.feature.group 3.0.0.Final-v20151002-2059-B50)
Software currently installed: JBoss Developer Studio (Branded Product) 9.0.1.Beta1-v20151105-0411-B134 (com.jboss.devstudio.core.package 9.0.1.Beta1-v20151105-0411-B134)
Only one of the following can be installed at once:
OpenShift Common UI 3.1.0.Beta1-v20151104-0336-B66 (org.jboss.tools.openshift.common.ui 3.1.0.Beta1-v20151104-0336-B66)
OpenShift Common UI 3.0.0.Final-v20151002-2059-B50 (org.jboss.tools.openshift.common.ui 3.0.0.Final-v20151002-2059-B50)
Cannot satisfy dependency:
From: JBoss Developer Studio (Core Features) 9.0.1.Beta1-v20151105-0411-B134 (com.jboss.devstudio.core.feature.feature.group 9.0.1.Beta1-v20151105-0411-B134)
To: org.jboss.tools.openshift.express.feature.feature.group [3.1.0.Beta1-v20151104-0336-B66]
Cannot satisfy dependency:
From: JBoss Developer Studio (Branded Product) 9.0.1.Beta1-v20151105-0411-B134 (com.jboss.devstudio.core.package 9.0.1.Beta1-v20151105-0411-B134)
To: com.jboss.devstudio.core.feature.feature.group [9.0.1.Beta1-v20151105-0411-B134]
Cannot satisfy dependency:
From: JBoss OpenShift 2 Tools 3.1.0.Beta1-v20151104-0336-B66 (org.jboss.tools.openshift.express.feature.feature.group 3.1.0.Beta1-v20151104-0336-B66)
To: org.jboss.tools.openshift.common.ui [3.1.0.Beta1-v20151104-0336-B66]
Cannot satisfy dependency:
From: JBoss OpenShift 3 Tools 3.0.0.Final-v20151002-2059-B50 (org.jboss.tools.openshift.feature.feature.group 3.0.0.Final-v20151002-2059-B50)
To: org.jboss.tools.openshift.common.ui [3.0.0.Final-v20151002-2059-B50]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21059) Server Adapter does not connect in debug mode on WF in a Docker container
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21059:
-------------------------------------
This issue is related to remote debugging not be present for any remote server. I'd suggest there's a slight difference in scope though.
I would guess the linked issue is for when launching a remote server in debug mode, to also set up a remote debugger.
I'd imagine this one is for externally-launched app servers (since we don't currently launch wildfly instances that are inside docker, do we?)
> Server Adapter does not connect in debug mode on WF in a Docker container
> --------------------------------------------------------------------------
>
> Key: JBIDE-21059
> URL: https://issues.jboss.org/browse/JBIDE-21059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
>
> I have a WF 9.0.2.Final in a Docker container, started with the debug flag in the command line :
> {code}
> CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone.xml", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0" , "--debug"]
> {code}
> I can connect to this server from the server adapter in Run mode but not in debug mode: the Debug view remains empty and the breakpoints are not hit.
> On the other side, I can connect using the plain Java remote debugger (in the launchers) and the same breakpoints are hit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21058) JSF tests fail
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21058?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21058:
-----------------------------------------------
Added PR removing recently set Test annotation from 'disabled' tests, with method names starting with '_test' prefix.
> JSF tests fail
> --------------
>
> Key: JBIDE-21058
> URL: https://issues.jboss.org/browse/JBIDE-21058
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha1
>
>
> Multiple failures are caused by
> java.lang.NoClassDefFoundError: Could not initialize class org.jboss.tools.jsf.ui.JsfUiPlugin$PluginHolder
> because of class cast exception at
> (JsfUiPlugin)Platform.getPlugin(PLUGIN_ID)
> since platform returned DefaultPlugin instead of JsfUiPlugin.
> Method Platform.getPlugin(String) is deprecated and probably works in the latest Eclipse not as before. Multiple failures (80 and more) started with build #52 on October 25, 2015. Build #51had only few failed tests.
> Pattern of initializing JsfUiPlugin is very uncommon and we should change it to the regular pattern in which static plugin instance is set in the constructor.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21059) Server Adapter does not connect in debug mode on WF in a Docker container
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21059:
---------------------------------------------
Also, this is probably not limited to docker - it is probably for any remote/externally managede server adapter.
There should be two things fixed:
A) if Debug mode can't actually connect a debugger the server adapter should not go into debugging mode - it should tell the user it cannot connect.
B) the server adapter should have or ask enough info to setup a remote debugging launch - just like it does if it started the server it self.
> Server Adapter does not connect in debug mode on WF in a Docker container
> --------------------------------------------------------------------------
>
> Key: JBIDE-21059
> URL: https://issues.jboss.org/browse/JBIDE-21059
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
>
> I have a WF 9.0.2.Final in a Docker container, started with the debug flag in the command line :
> {code}
> CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone.xml", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0" , "--debug"]
> {code}
> I can connect to this server from the server adapter in Run mode but not in debug mode: the Debug view remains empty and the breakpoints are not hit.
> On the other side, I can connect using the plain Java remote debugger (in the launchers) and the same breakpoints are hit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21059) Server Adapter does not connect in debug mode on WF in a Docker container
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-21059:
-------------------------------------
Summary: Server Adapter does not connect in debug mode on WF in a Docker container
Key: JBIDE-21059
URL: https://issues.jboss.org/browse/JBIDE-21059
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.0.Final
Reporter: Xavier Coulon
I have a WF 9.0.2.Final in a Docker container, started with the debug flag in the command line :
{code}
CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone.xml", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0" , "--debug"]
{code}
I can connect to this server from the server adapter in Run mode but not in debug mode: the Debug view remains empty and the breakpoints are not hit.
On the other side, I can connect using the plain Java remote debugger (in the launchers) and the same breakpoints are hit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21057) Web Services Tester locks up when editing
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21057?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick edited comment on JBIDE-21057 at 11/5/15 4:30 PM:
--------------------------------------------------------------------
Apparently the simpler case seems to work on Jane's Mac (i.e. it doesn't lock up the way it does when going against a WSDL in a server).
[~apodhrad] Can you try the full reproduction steps in the attachment on a Mac? Wondering what's going on here...
was (Author: bfitzpat):
Apparently the simpler case seems to work on Jane's Mac. [~apodhrad] Can you try the full reproduction steps in the attachment? Wondering what's going on here...
> Web Services Tester locks up when editing
> ------------------------------------------
>
> Key: JBIDE-21057
> URL: https://issues.jboss.org/browse/JBIDE-21057
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.3.Final
> Environment: Mac setup:
> • OS X 10.9.4
> • JBDS 8.1.0.GA-v20150327-1349-B467
> • Fuse Tooling 7.2.3.v20151008-1250-H108-CR2
> • Switchyard 2.0.1v20150923-1505-H19-CR1
> • JRE 1.7.0_25-b15
> Reporter: Jane Murphey
> Assignee: Brian Fitzpatrick
> Priority: Critical
> Attachments: OSX_WebServicTesterHang.rtf
>
>
> When using the tree view in the Web Service Tester to edit request message values, the entire workbench freezes. Nothing appears in the error log and I have been unable to reproduce in a Windows environment.
> Will get a simpler reproducible case, but am posting what [~jmurphey] has documented so far.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months