August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3931) Installed OC binary is not used by default if user has another OC already on system path

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3931?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3931: ----------------------------------- I'm not saying oc is not added to PATH, it is. What happened here was the machine already had another instance of oc installed and added to system PATH (not the user PATH, if that makes any difference). When I installed everything, devstudio started using the previously installed oc by default. > Installed OC binary is not used by default if user has another OC already on system path > ---------------------------------------------------------------------------------------- > > Key: JBDS-3931 > URL: https://issues.jboss.org/browse/JBDS-3931 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > > I tried to install everything on a machine where an existing OC binary was already on path. The newly installed devstudio then used it by default instead of the bundled one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22969: --------------------------------------- Well I think we probably have a problem. There are still appended rules for UDP and TCP to use proxy, but you also set policy to accept all. So I guess, but I am not sure, that it probably works on different ports and thus you are not able to create docker connection or OS connection when you have only 3128 port allowed. It seems vagrant service manager operates on a different port. But I have never worked with this before so this is just a hunch. > Make sure OpenShift Tools support proxies > ----------------------------------------- > > Key: JBIDE-22969 > URL: https://issues.jboss.org/browse/JBIDE-22969 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Dmitrii Bocharov > Fix For: 4.4.1.Final > > Attachments: proxy_settings.png > > > CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too. > If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side. > This issue covers: > - testing > - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests) > - fixing any problems we have in OpenShift tooling regarding proxy support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3931) Installed OC binary is not used by default if user has another OC already on system path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3931?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3931: ------------------------------------- [~jrichter1] I cannot replicate that issue. I always get cdk/bin (where oc is unpacked) folder added at the beginning of PATH var. In code you can see it here [cdk.js:137|https://github.com/redhat-developer-tooling/developer-platform...]. > Installed OC binary is not used by default if user has another OC already on system path > ---------------------------------------------------------------------------------------- > > Key: JBDS-3931 > URL: https://issues.jboss.org/browse/JBDS-3931 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > > I tried to install everything on a machine where an existing OC binary was already on path. The newly installed devstudio then used it by default instead of the bundled one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22746) Port forwarding shell is not opened

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22746?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22746. --------------------------------- Back to normal, verified as part of devstudio 10.1.0 AM3 testing. > Port forwarding shell is not opened > ----------------------------------- > > Key: JBIDE-22746 > URL: https://issues.jboss.org/browse/JBIDE-22746 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v2 > Fix For: 4.4.1.Final > > > When I select a context menu item in context menu of an OpenShift 2 application, Port Forwarding dialog is not opened. Right after click on the item there is a running job Verifying SSH session but once its finished, nothing happens. There is even no error/warning in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22747) Several context menu items in context menu of an OpenShift 2 server adapter do not work

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22747?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22747: --------------------------------------- Well basically this is not a duplicate. Cause is the same but this JIRA is about something else so I am not quite sure whether duplicate is relevant solution ;) But in the end, this is already fixed and context menu items work. Verified while testing AM3 build. > Several context menu items in context menu of an OpenShift 2 server adapter do not work > --------------------------------------------------------------------------------------- > > Key: JBIDE-22747 > URL: https://issues.jboss.org/browse/JBIDE-22747 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v2 > Fix For: 4.4.1.Final > > > When I click on some context menu items on OpenShift 2 Server adapter, nothing happens. It works when opened via context menu of an application in OpenShift explorer view. > Following context menu items are not working: > - OpenShift - Port Forwarding... > - OpenShift - Tail Files... > - OpenShift - Snapshot - Save... > - OpenShift - Snapshot - Restore/Deploy... > - OpenShift - Details... > - OpenShift - Edit Embedded Cartridges... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22747) Several context menu items in context menu of an OpenShift 2 server adapter do not work

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22747?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22747. --------------------------------- > Several context menu items in context menu of an OpenShift 2 server adapter do not work > --------------------------------------------------------------------------------------- > > Key: JBIDE-22747 > URL: https://issues.jboss.org/browse/JBIDE-22747 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v2 > Fix For: 4.4.1.Final > > > When I click on some context menu items on OpenShift 2 Server adapter, nothing happens. It works when opened via context menu of an application in OpenShift explorer view. > Following context menu items are not working: > - OpenShift - Port Forwarding... > - OpenShift - Tail Files... > - OpenShift - Snapshot - Save... > - OpenShift - Snapshot - Restore/Deploy... > - OpenShift - Details... > - OpenShift - Edit Embedded Cartridges... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20362) Extracting of a download runtime is slow on Mac

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20362?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20362: --------------------------------------- [~rob.stryker], I agree that it seems crazy and I will have to test this several more times to have more certainty about this. But it really seemed to me that it must be synchronous then. But today I'm at home where the speed is much slower, so I will have to wait for Monday. > Extracting of a download runtime is slow on Mac > ----------------------------------------------- > > Key: JBIDE-20362 > URL: https://issues.jboss.org/browse/JBIDE-20362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > While playing with the Download runtime fuctionality, I noticed that once a runtime (e.g. EAP 6.2) is downloaded, the extraction takes very long. I think it used to be fast and the extraction was done without any progress reporting. But now it seems that every subdirectory in the archive is being printed out which slows it down. > This extraction process took 1 min 23 sec for EAP 6.2 and I have an SSD. On a command line, this would take a few seconds. > I think the solution may be to simply show "Extracting" without printing out each file/directory that is being extracted. > (Furthermore, the progress bar does not reflect the progress - it seems there is still only perhaps 5 % done and then it's suddenly over.) > I can record a screencast if you like, but I think this should be easy to replicate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-822) Create a test for manipulating with 2 routes

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-822?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-822. ------------------------------ Fix Version/s: 4.3.1.Final Resolution: Done pushed to master branch > Create a test for manipulating with 2 routes > -------------------------------------------- > > Key: JBTIS-822 > URL: https://issues.jboss.org/browse/JBTIS-822 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-836) Update the logic for adding a new component according to FUSETOOLS-1976

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-836?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík commented on JBTIS-836: ------------------------------------ That is great. With this feature the tests will be more stable (AWT Robot for creating connections between components is no longer needed). I will do it as soon as I can ;-). > Update the logic for adding a new component according to FUSETOOLS-1976 > ----------------------------------------------------------------------- > > Key: JBTIS-836 > URL: https://issues.jboss.org/browse/JBTIS-836 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final > Reporter: Andrej Podhradsky > Assignee: Tomáš Sedmík > > Update the logic for adding a new component according to FUSETOOLS-1976. Now, we can just click on the component we want connect to. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4007) Need a new check for existing OpenJDK installed as an msi package

by Alex Kashchenko (JIRA)

[ https://issues.jboss.org/browse/JBDS-4007?page=com.atlassian.jira.plugin.... ] Alex Kashchenko commented on JBDS-4007: --------------------------------------- I am confirming, that for 8u91 and 8u101 the described logic is the expected one. MSI upgrade feature was not included for them so each release was a "different non-upgradeable version of the same product". Upgrade feature was included starting from 8u102-1 release, current logic is the following: 1) 8u101 installed: - later versions can be installed, 8u101 will be silently removed during the installation - earlier versions cannot be installed, "Another version of this product is already installed. ..." message will be shown 2) 8u102-1 installed: - 8u101 can be installed and will be installed side by side with 8u102-1. I currently see no workaround to prevent this, as 8u101 doesn't have update logic to prevent this - 8u102-2 can be installed, 8u102-1 will be silently removed during the installation 3) 8u102-2 installed: - 8u101 can be installed and will be installed side by side with 8u102-2 (see above) - 8u102-1 cannot be installed, "A later version of [ProductName] is already installed. Setup will now exit." message will be shown. For all versions, running the installer for the version that is already installed will show the "Repair" menu on the second installer screen. If current upgrade logic is not sufficient, I can change (for 8u102 and later) it as will be required. > Need a new check for existing OpenJDK installed as an msi package > ----------------------------------------------------------------- > > Key: JBDS-4007 > URL: https://issues.jboss.org/browse/JBDS-4007 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.1.0.GA > > Attachments: openjdk.log, screenshot-1.png > > > Now that OpenJDK is being installed using the msi installer, a new possible issue has arisen: > Basically it's the same problem we had with Vagrant and Virtualbox - one cannot simply try to reinstall msi package into a different folder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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