January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16879) Explorer: context menu for cartridges opens away from cartridge

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16879?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16879: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Explorer: context menu for cartridges opens away from cartridge > --------------------------------------------------------------- > > Key: JBIDE-16879 > URL: https://issues.jboss.org/browse/JBIDE-16879 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.2.0.Beta1 > Environment: Fedora 19, 64-bit, java version "1.7.0_51", OpenJDK Runtime Environment (fedora-2.4.5.0.fc19-x86_64 u51-b31) GTK3 > Reporter: Michelle Murray > Assignee: Jeff MAURY > Priority: Minor > Labels: explorer, gtk3, openshift_v2, openshift_v3, upstream > Fix For: 4.4.x > > Attachments: OpenShift_conmenu.png > > > In OpenShift Explorer view, expand tree down to cartridge level for an app. Right-click cartridge. The context menu opens away from mouse pointer rather than adjacent to it as it does for other tree items, like connection, domain or app. > I can 100% of time reproduce it by first right-clicking app and then immediately right-clicking (twice) cartridge. > I can't reproduce it by first right-clicking connection or domain and then immediately right-clicking (twice) cartridge. > !OpenShift_conmenu.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16879) Explorer: context menu for cartridges opens away from cartridge

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16879?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16879: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.3.AM2) > Explorer: context menu for cartridges opens away from cartridge > --------------------------------------------------------------- > > Key: JBIDE-16879 > URL: https://issues.jboss.org/browse/JBIDE-16879 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.2.0.Beta1 > Environment: Fedora 19, 64-bit, java version "1.7.0_51", OpenJDK Runtime Environment (fedora-2.4.5.0.fc19-x86_64 u51-b31) GTK3 > Reporter: Michelle Murray > Assignee: Jeff MAURY > Priority: Minor > Labels: explorer, gtk3, openshift_v2, openshift_v3, upstream > Fix For: 4.4.x > > Attachments: OpenShift_conmenu.png > > > In OpenShift Explorer view, expand tree down to cartridge level for an app. Right-click cartridge. The context menu opens away from mouse pointer rather than adjacent to it as it does for other tree items, like connection, domain or app. > I can 100% of time reproduce it by first right-clicking app and then immediately right-clicking (twice) cartridge. > I can't reproduce it by first right-clicking connection or domain and then immediately right-clicking (twice) cartridge. > !OpenShift_conmenu.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23626: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: oc_binary, preferences > Fix For: 4.4.3.AM2 > > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3 (it's only compatible oc 1.3). Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use compatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21857: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Hot code replacement doesn't work on OpenShift > ---------------------------------------------- > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.4.3.AM2 > > Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23131) Integration tests: move openshift integration tests to jbosstools/openshift repo

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23131?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23131: ------------------------------------- Sprint: devex #123 November 2016, devex #126 January 2017 (was: devex #123 November 2016) > Integration tests: move openshift integration tests to jbosstools/openshift repo > -------------------------------------------------------------------------------- > > Key: JBIDE-23131 > URL: https://issues.jboss.org/browse/JBIDE-23131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration-test > Fix For: 4.4.3.AM2 > > Original Estimate: 1 day > Time Spent: 4 hours > Remaining Estimate: 4 hours > > we need to move jbosstools/openshift integration tests from their [repo|https://github.com/jbosstools/jbosstools-integration-tests] to the jbosstools/openshift tools [repo|https://github.com/jbosstools/jbosstools-openshift] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23625) JMX: jmx tree is not very usable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23625?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23625: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > JMX: jmx tree is not very usable > -------------------------------- > > Key: JBIDE-23625 > URL: https://issues.jboss.org/browse/JBIDE-23625 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Fix For: 4.4.3.AM2 > > Attachments: image-2016-12-02-16-47-59-519.png > > > steps to reproduce: > # EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project > # EXEC: create a server adapter for it > # ASSERT: your server adapter now has a JMX child node > # EXEC: double click it and wait until all MBeans are loaded > # EXEC: now try to see if you can find your deployment > Result: > You get a listing of tons of beans. > !mbeans.png! > Your deployment is a child bean of jboss.as, named by the war that was created: > !mbean-deployment.png! > Rather painfull to find a listing of your deployments in this way. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23638) Scaling: Sometimes incorrect version of RC leads to error when scaling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23638?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23638: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Scaling: Sometimes incorrect version of RC leads to error when scaling > ---------------------------------------------------------------------- > > Key: JBIDE-23638 > URL: https://issues.jboss.org/browse/JBIDE-23638 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.3.AM2 > > > Sometimes when scaling an OpenShift 3 application several times, there is an error about failed PUT call. No jobs are running when triggering a scaling. Even though pods are shown correctly (right amount is shown) this error is shown: > {code} > com.openshift.restclient.OpenShiftException: Exception trying to PUT https://10.1.2.2:8443/api/v1/namespaces/test-project/replicationcontrolle... response code: 409 Operation cannot be fulfilled on replicationcontrollers "nodejs-example-1": the object has been modified; please apply your changes to the latest version and try again > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65) > at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163) > at okhttp3.RealCall.execute(RealCall.java:57) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275) > at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451) > at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler$2.run(ScaleDeploymentHandler.java:155) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23279) Exception generated when OS 3 connection URL is invalid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23279?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23279: ------------------------------------- Sprint: devex #126 January 2017 > Exception generated when OS 3 connection URL is invalid > ------------------------------------------------------- > > Key: JBIDE-23279 > URL: https://issues.jboss.org/browse/JBIDE-23279 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3 > Fix For: 4.4.3.AM2 > > > EXEC: launch application wizard via file menu: New > OpenShift > OpenShift application > EXEC: select <New Connection> > EXEC: enter invalid URL in the host field > ASSERT: an com.openshift.restclient.OpenShiftException: Unable to initialize client exception is logged into the console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23131) Integration tests: move openshift integration tests to jbosstools/openshift repo

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23131?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23131: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Integration tests: move openshift integration tests to jbosstools/openshift repo > -------------------------------------------------------------------------------- > > Key: JBIDE-23131 > URL: https://issues.jboss.org/browse/JBIDE-23131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration-test > Fix For: 4.4.3.AM2 > > Original Estimate: 1 day > Time Spent: 4 hours > Remaining Estimate: 4 hours > > we need to move jbosstools/openshift integration tests from their [repo|https://github.com/jbosstools/jbosstools-integration-tests] to the jbosstools/openshift tools [repo|https://github.com/jbosstools/jbosstools-openshift] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23279) Exception generated when OS 3 connection URL is invalid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23279?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23279: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Exception generated when OS 3 connection URL is invalid > ------------------------------------------------------- > > Key: JBIDE-23279 > URL: https://issues.jboss.org/browse/JBIDE-23279 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.4.3.AM2 > > > EXEC: launch application wizard via file menu: New > OpenShift > OpenShift application > EXEC: select <New Connection> > EXEC: enter invalid URL in the host field > ASSERT: an com.openshift.restclient.OpenShiftException: Unable to initialize client exception is logged into the console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017