December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21318) OpenShift 2 Server Adapter contains label "... at OpenShift 3"

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21318: ------------------------------------- Summary: OpenShift 2 Server Adapter contains label "... at OpenShift 3" Key: JBIDE-21318 URL: https://issues.jboss.org/browse/JBIDE-21318 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Marián Labuda OpenShift 2 server adapters contains in name "... at OpenShift 3". E.g. "applicationName at OpenShift 3". This should be as it was earlier "... at OpenShift" or to distinguish between 2 and 3 we could use "... at OpenShift 2". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21318) OpenShift 2 Server Adapter contains label "... at OpenShift 3"

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21318?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21318: ---------------------------------- Labels: server_adapter (was: ) > OpenShift 2 Server Adapter contains label "... at OpenShift 3" > --------------------------------------------------------------- > > Key: JBIDE-21318 > URL: https://issues.jboss.org/browse/JBIDE-21318 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: server_adapter > > OpenShift 2 server adapters contains in name "... at OpenShift 3". E.g. "applicationName at OpenShift 3". This should be as it was earlier "... at OpenShift" or to distinguish between 2 and 3 we could use "... at OpenShift 2". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20692) Cheatsheet dialog should have ok/cancel buttons, not yes/no

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20692?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-20692. ------------------------------ Verified in JBDS 9.1.0.Beta1-v20151212-0638-B189 > Cheatsheet dialog should have ok/cancel buttons, not yes/no > ----------------------------------------------------------- > > Key: JBIDE-20692 > URL: https://issues.jboss.org/browse/JBIDE-20692 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Fred Bricon > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: cheatsheet.png > > > Not sure on what component this belongs to. Cheatsheet dialog should have ok/cancel buttons, not yes/no -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21298) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21298?page=com.atlassian.jira.plugi... ] Rob Stryker edited comment on JBIDE-21298 at 12/14/15 8:48 AM: --------------------------------------------------------------- This is most likely a result of https://issues.jboss.org/browse/JBIDE-21192 which was an intentional change in behavior and forgetting to update the unit tests. was (Author: rob.stryker): This is most likely a result of https://issues.jboss.org/browse/JBIDE-21192 which was an intentional change in behavior without updating the unit tests. > 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component > ---------------------------------------------------------------------- > > Key: JBIDE-21298 > URL: https://issues.jboss.org/browse/JBIDE-21298 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Critical > Labels: testfailure > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component:* > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m... > # [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for runtime-detection component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds) > > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths} > <case> > <age>5</age> > <className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className> > <duration>0.0050</duration> > <errorDetails>/qa/services/hudson/jboss-runtimes > expected:<0> but was:<1></errorDetails> > <errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes > expected:<0> but was:<1> > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.failNotEquals(Assert.java:329) > at junit.framework.Assert.assertEquals(Assert.java:78) > at junit.framework.Assert.assertEquals(Assert.java:234) > at junit.framework.TestCase.assertEquals(TestCase.java:401) > at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73) > </errorStackTrace> > <failedSince>58</failedSince> > <name>testLoadSaveRuntimePaths</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21298) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21298?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21298: ------------------------------------- This is most likely a result of https://issues.jboss.org/browse/JBIDE-21192 which was an intentional change in behavior without updating the unit tests. > 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component > ---------------------------------------------------------------------- > > Key: JBIDE-21298 > URL: https://issues.jboss.org/browse/JBIDE-21298 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Critical > Labels: testfailure > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for runtime-detection component:* > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.m... > # [org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest|http://jenkins...] (failing for 5 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for runtime-detection component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest : testLoadSaveRuntimePaths{color} (failing for 5 builds) > > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_4.3.mars/62/testReport/org.jboss.tools.runtime.test/RuntimeDetectionFrameworkTest/testLoadSaveRuntimePaths} > <case> > <age>5</age> > <className>org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest</className> > <duration>0.0050</duration> > <errorDetails>/qa/services/hudson/jboss-runtimes > expected:<0> but was:<1></errorDetails> > <errorStackTrace>junit.framework.AssertionFailedError: /qa/services/hudson/jboss-runtimes > expected:<0> but was:<1> > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.failNotEquals(Assert.java:329) > at junit.framework.Assert.assertEquals(Assert.java:78) > at junit.framework.Assert.assertEquals(Assert.java:234) > at junit.framework.TestCase.assertEquals(TestCase.java:401) > at org.jboss.tools.runtime.test.RuntimeDetectionFrameworkTest.testLoadSaveRuntimePaths(RuntimeDetectionFrameworkTest.java:73) > </errorStackTrace> > <failedSince>58</failedSince> > <name>testLoadSaveRuntimePaths</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21173) Runtime detection not working for CDK 2 Beta3

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21173?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21173. --------------------------------- Yeah, the build available from CSP still doesn't have the marker AFAIK. But we will definitely require for it to be there when we consume CDK for PDK. And I verified that runtime detection works now with what is available at https://github.com/redhat-developer-tooling/openshift-vagrant . So I'm confident to close this JIRA. > Runtime detection not working for CDK 2 Beta3 > --------------------------------------------- > > Key: JBIDE-21173 > URL: https://issues.jboss.org/browse/JBIDE-21173 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1 > > > When I point runtime detection to my cdk folder, it will not detect anything. > I had the openshift.cdk feature installed. > {code} > nattura:features rasp$ ls|grep cdk > org.jboss.tools.openshift.cdk.feature_3.1.0.Beta1-v20151202-0847-B100 > {code} > And the runtime detection preference page shows that it will search for cdk runtimes > (CDK is checked). > The cdk in the folder that I use work fine when I add the adapter manually. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21313) No web console URL for connection, project and resources

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21313?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21313: ------------------------------------- This is a regression caused by https://github.com/jbosstools/jbosstools-openshift/commit/740300f67d65f26... {code} - openInBrowser(HandlerUtil.getActiveShell(event) , url); + if (!StringUtils.isEmpty(url)) { + MessageDialog.openWarning(HandlerUtil.getActiveShell(event), + "No Web Console Url", + NLS.bind("Could not determine the url for the web console on {0}", connection.getHost())); + } {code} > No web console URL for connection, project and resources > -------------------------------------------------------- > > Key: JBIDE-21313 > URL: https://issues.jboss.org/browse/JBIDE-21313 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Attachments: no_web_console_url.png > > > When trying to open OpenShift 3 connection, project or any resource in web console via context menu Show In - Web Console, there is following error: > !no_web_console_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21313) No web console URL for connection, project and resources

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21313?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21313: ----------------------------------- Assignee: Andre Dietisheim > No web console URL for connection, project and resources > -------------------------------------------------------- > > Key: JBIDE-21313 > URL: https://issues.jboss.org/browse/JBIDE-21313 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Attachments: no_web_console_url.png > > > When trying to open OpenShift 3 connection, project or any resource in web console via context menu Show In - Web Console, there is following error: > !no_web_console_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21294) NPE when starting CDK server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21294?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21294. --------------------------------- Verified in jboss-devstudio-9.1.0.Beta1-v20151212-0638-B189-installer-standalone.jar > NPE when starting CDK server > ---------------------------- > > Key: JBIDE-21294 > URL: https://issues.jboss.org/browse/JBIDE-21294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > I've been testing the CDK adapter with [1] today and when I tried to start again from scratch (vagrant destroy + new workspace) and added the server again and started, I got a NPE: > {code} > An internal error occurred during: "Starting cdk-v2 CDK Server". > java.lang.NullPointerException > at java.io.File.<init>(File.java:277) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:133) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > I did add the user credentials in the server editor. > Now I looked in the launch config and the first field at the top is empty - it should contain path to vagrant. I'm not sure why it's missing - I just used runtime detection. But in any case, the NPE should be handled somehow. > [1] https://github.com/redhat-developer-tooling/openshift-vagrant -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21294) NPE when starting CDK server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21294?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21294: --------------------------------------- There is now a proper error message in place, great! {code} Unable to locate vagrant command. Please check to ensure that the command is available on your Path environment variable. {code} To answer your question about tracing. I found out why it worked for me in one instance and not the other - as discussed previously, PATH is not set up when you start Eclipse by double-clicking the app in Finder. But when I run the JBDS installer from command line (which I usually do) and then after installation the installer launches JBDS for me, it will inherit PATH, so during runtime detection, the path to vagrant is set up correctly and it works until you restart your IDE. I logged JBIDE-21315 to track this issue. But the NPE is solved so this JIRA can be closed. > NPE when starting CDK server > ---------------------------- > > Key: JBIDE-21294 > URL: https://issues.jboss.org/browse/JBIDE-21294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > I've been testing the CDK adapter with [1] today and when I tried to start again from scratch (vagrant destroy + new workspace) and added the server again and started, I got a NPE: > {code} > An internal error occurred during: "Starting cdk-v2 CDK Server". > java.lang.NullPointerException > at java.io.File.<init>(File.java:277) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:133) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > I did add the user credentials in the server editor. > Now I looked in the launch config and the first field at the top is empty - it should contain path to vagrant. I'm not sure why it's missing - I just used runtime detection. But in any case, the NPE should be handled somehow. > [1] https://github.com/redhat-developer-tooling/openshift-vagrant -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2015