March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21917) oc rsync waits forever on windows

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21917?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21917: ---------------------------------------- It might be fixed by now but we still need to verify it on Windows. > oc rsync waits forever on windows > --------------------------------- > > Key: JBIDE-21917 > URL: https://issues.jboss.org/browse/JBIDE-21917 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Environment: Windows 10 > Reporter: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.CR1 > > > On windows 10 + CDK 2 Beta5, oc rsync is stuck until it times out when saving a file, autopublished via the server adapter > {noformat} > "Worker-7" #48 prio=5 os_prio=0 tid=0x000000001bc85000 nid=0x1928 runnable [0x00000000275ee000] > java.lang.Thread.State: RUNNABLE > at java.lang.ProcessImpl.waitForTimeoutInterruptibly(Native Method) > at java.lang.ProcessImpl.waitFor(Unknown Source) > at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.waitForExit(OpenShiftBinaryRSync.java:59) > at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.sync(OpenShiftBinaryRSync.java:50) > at org.jboss.tools.openshift.core.server.RSync$1.visit(RSync.java:102) > at org.jboss.tools.openshift.core.server.RSync$1.visit(RSync.java:1) > at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91) > at org.jboss.tools.openshift.core.server.RSync.syncPodToDirectory(RSync.java:99) > at org.jboss.tools.openshift.core.server.RSync.syncPodsToDirectory(RSync.java:67) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:84) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) > at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172) > at org.eclipse.wst.server.core.internal.Server.publish(Server.java:1330) > at org.jboss.tools.openshift.internal.core.server.resources.OpenshiftResourceChangeListener$MagicProjectChangeJob.autoPublish(OpenshiftResourceChangeListener.java:227) > at org.jboss.tools.openshift.internal.core.server.resources.OpenshiftResourceChangeListener$MagicProjectChangeJob.run(OpenshiftResourceChangeListener.java:208) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21917) oc rsync waits forever on windows

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21917?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21917: -------------------------------------- Assignee: Fred Bricon > oc rsync waits forever on windows > --------------------------------- > > Key: JBIDE-21917 > URL: https://issues.jboss.org/browse/JBIDE-21917 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Environment: Windows 10 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.CR1 > > > On windows 10 + CDK 2 Beta5, oc rsync is stuck until it times out when saving a file, autopublished via the server adapter > {noformat} > "Worker-7" #48 prio=5 os_prio=0 tid=0x000000001bc85000 nid=0x1928 runnable [0x00000000275ee000] > java.lang.Thread.State: RUNNABLE > at java.lang.ProcessImpl.waitForTimeoutInterruptibly(Native Method) > at java.lang.ProcessImpl.waitFor(Unknown Source) > at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.waitForExit(OpenShiftBinaryRSync.java:59) > at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.sync(OpenShiftBinaryRSync.java:50) > at org.jboss.tools.openshift.core.server.RSync$1.visit(RSync.java:102) > at org.jboss.tools.openshift.core.server.RSync$1.visit(RSync.java:1) > at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91) > at org.jboss.tools.openshift.core.server.RSync.syncPodToDirectory(RSync.java:99) > at org.jboss.tools.openshift.core.server.RSync.syncPodsToDirectory(RSync.java:67) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishStart(OpenShiftPublishController.java:84) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishStart(CachedPublisherProfileBehavior.java:47) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) > at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172) > at org.eclipse.wst.server.core.internal.Server.publish(Server.java:1330) > at org.jboss.tools.openshift.internal.core.server.resources.OpenshiftResourceChangeListener$MagicProjectChangeJob.autoPublish(OpenshiftResourceChangeListener.java:227) > at org.jboss.tools.openshift.internal.core.server.resources.OpenshiftResourceChangeListener$MagicProjectChangeJob.run(OpenshiftResourceChangeListener.java:208) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21949) Allow user to turn on/off showing console when output changes

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21949?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-21949. ------------------------------------ Resolution: Done Resolving. Marian please create a new issue for that. > Allow user to turn on/off showing console when output changes > ------------------------------------------------------------- > > Key: JBIDE-21949 > URL: https://issues.jboss.org/browse/JBIDE-21949 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.1.CR1 > > > At the moment every publish to OpenShift via rsync show console with output from rsync (done in JBIDE-21326). User is forced to see console output. It would be nice if I could disable/enable showing console output when content changes. Something like server's console output has - toggle button Show Console Output When Standard Out Changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3738) Getting Started / Readme for new users after Dev Platform install is complete

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3738?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3738: ------------------------------------- We decided to have a link on last page of installer to external page. The external page we are going to use is http://developers.redhat.com/products/cdk/get-started/. There is no need to create any additional files or readme files. > Getting Started / Readme for new users after Dev Platform install is complete > ----------------------------------------------------------------------------- > > Key: JBDS-3738 > URL: https://issues.jboss.org/browse/JBDS-3738 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Labels: Havoc > Fix For: 9.1.0.CR1 > > > Per discussion today, we need some sort of README / Getting Started Guide for new CDK users. > This could be a link from the last page of the Dev Platform installer to a remote HTML page, but we could also include a copy of that HTML page in the c:\devplatform folder so people can refer to it offline. > Need to decide where to locate the page online. If the doc can be available before April 12, it could potentially be included in the output of the installer for offline use too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21997) Aeri causes NPE when running unittests

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21997?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21997: ------------------------------------ Note: if we don't have a build-time dependency to a specific version of Aeri 1.100... we could just update the TP used for install/testing (4.52.x) to include the newer version. Then there's no problem w/ changing jetty version since we would not be updating the 4.50.x TP. We follow this model for most things in Mars -- build with minimum compatible version (1.100.0.v20160217-0435), install & run tests on best/latest version (1.100.0.v20160304-1116). Thoughts? > Aeri causes NPE when running unittests > -------------------------------------- > > Key: JBIDE-21997 > URL: https://issues.jboss.org/browse/JBIDE-21997 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aeri, target-platform > Affects Versions: 4.3.1.CR1 > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.3.1.CR1 > > > an Eclipse bug was fixed 4 weeks ago in AERi and we need this fix to launch Integration tests for JBoss Fuse Tooling. > We need the version containing the fix of https://bugs.eclipse.org/bugs/show_bug.cgi?id=488868 > Seems that we need to use the org.eclipse.epp.logging.aeri.core_1.100.0.v20160304-1116.jar although we are using org.eclipse.epp.logging.aeri.core_1.100.0.v20160211-1103 > Please take care because the version number are both 1.100.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21998) "Open in Web browser" displays a dialog to select a route

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21998?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21998: ------------------------------------------ I believe ResourceUtils#getRouteForService should give us the routes for a given service if we get only 1 route, we're fine, no need for the dialog. Otherwise we should show the dialog. > "Open in Web browser" displays a dialog to select a route > --------------------------------------------------------- > > Key: JBIDE-21998 > URL: https://issues.jboss.org/browse/JBIDE-21998 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > Attachments: Screenshot 2016-03-30 00.20.48.png > > > I have an OpenShift project with 2 services: one {{eap-app}} and one NodeJS. > For the {{eap-app}} service, I have a corresponding server adapter. > When I select {{<eap-app server adapter> > Show In > Web Browser}}, I have the following dialog to select a route, but that seems wrong because I already selected the {{eap-app}} service, so there's no reason to propose me the route to the NodeJS service. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3738) Getting Started / Readme for new users after Dev Platform install is complete

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3738?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3738: -------------------------------- Labels: Havoc (was: ) > Getting Started / Readme for new users after Dev Platform install is complete > ----------------------------------------------------------------------------- > > Key: JBDS-3738 > URL: https://issues.jboss.org/browse/JBDS-3738 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Labels: Havoc > Fix For: 9.1.0.CR1 > > > Per discussion today, we need some sort of README / Getting Started Guide for new CDK users. > This could be a link from the last page of the Dev Platform installer to a remote HTML page, but we could also include a copy of that HTML page in the c:\devplatform folder so people can refer to it offline. > Need to decide where to locate the page online. If the doc can be available before April 12, it could potentially be included in the output of the installer for offline use too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21836) Preferences: openshift 3 oc location resets to a different/old value on restart

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21836?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21836: ---------------------------------------- It seems that we can't reproduce it but it still requires investigation. Moving to 4.4.0 > Preferences: openshift 3 oc location resets to a different/old value on restart > ------------------------------------------------------------------------------- > > Key: JBIDE-21836 > URL: https://issues.jboss.org/browse/JBIDE-21836 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.4.0.Alpha1 > > > on start of eclipse new workspace the value is for reason unknown to me set to: > {code} > /Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc > {code} > which does exist, but is old version and publish fails. > Then I set it to > {code} > /usr/local/bin/oc > {code} > now publish works. > Restart eclipse - old value returns and publish starts failing again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21836) Preferences: openshift 3 oc location resets to a different/old value on restart

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21836?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21836: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > Preferences: openshift 3 oc location resets to a different/old value on restart > ------------------------------------------------------------------------------- > > Key: JBIDE-21836 > URL: https://issues.jboss.org/browse/JBIDE-21836 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.4.0.Alpha1 > > > on start of eclipse new workspace the value is for reason unknown to me set to: > {code} > /Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc > {code} > which does exist, but is old version and publish fails. > Then I set it to > {code} > /usr/local/bin/oc > {code} > now publish works. > Restart eclipse - old value returns and publish starts failing again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21836) Preferences: openshift 3 oc location resets to a different/old value on restart

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21836?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21836: -------------------------------------- Assignee: Rob Stryker (was: Max Rydahl Andersen) > Preferences: openshift 3 oc location resets to a different/old value on restart > ------------------------------------------------------------------------------- > > Key: JBIDE-21836 > URL: https://issues.jboss.org/browse/JBIDE-21836 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.4.0.Alpha1 > > > on start of eclipse new workspace the value is for reason unknown to me set to: > {code} > /Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc > {code} > which does exist, but is old version and publish fails. > Then I set it to > {code} > /usr/local/bin/oc > {code} > now publish works. > Restart eclipse - old value returns and publish starts failing again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 March 2016