October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23315) Connection wizard: "Advanced >>" Button is cropped

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23315?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23315: ------------------------------------ Yes I can reproduce and that's because space is reserved for the extended properties > Connection wizard: "Advanced >>" Button is cropped > -------------------------------------------------- > > Key: JBIDE-23315 > URL: https://issues.jboss.org/browse/JBIDE-23315 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Priority: Minor > Labels: connection_wizard > Fix For: 4.4.x > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23320) New server window server type picker is single line long on Cinnamon

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23320?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23320: ------------------------------------ I think there is a problem on Fedora24/Cinnamon where the server type (TreeViewer ?) is displayed on a single line when this is not the case on Fedora23. > New server window server type picker is single line long on Cinnamon > -------------------------------------------------------------------- > > Key: JBIDE-23320 > URL: https://issues.jboss.org/browse/JBIDE-23320 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Fedora 24 x86-64 > Cinnamon 3.0.7 > Linux 4.7.6 > JBDS 10.1.0.GA > Reporter: Michal Jurc > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > Attachments: jbds-10.1-new-server.png > > > In JBoss Developer Studio 10.1.0.GA, the New Server window server type choice only displays single server at time without scrolling which is uncomfortable to navigate through. > Screenshot attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22965: -------------------------------- Description: Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. We should make sure our CDK tooling supports it too. In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: {noformat} lalatenduM: we exepect customers workstation is configured to porixy server that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work lalatenduM: on a customer worksttaion lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information lalatenduM: vagrant-registration uses subscription manager for registraton lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info {noformat} was: Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. We should make sure our CDK tooling supports it too. In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: {noformat} lalatenduM: we exepect customers workstation is configured to porixy server that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work lalatenduM: on a customer worksttaion lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information lalatenduM: vagrant-registration uses subscription manager for registraton lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info {noformat} > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM2 > > Attachments: create_proxy-test_env.sh > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. > In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... > Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 > + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 > Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: > {noformat} > lalatenduM: we exepect customers workstation is configured to porixy server > that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work > lalatenduM: on a customer worksttaion > lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information > lalatenduM: vagrant-registration uses subscription manager for registraton > lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Xavier Coulon commented on JBDS-3903: ------------------------------------- [~mhusnain], Thanks ! This looks good to me now ;-) > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: docker > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Misha Ali > Fix For: 10.2.0.AM3 > > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23179) "not_created" not recognized as a vagrant state in master

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23179?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23179. --------------------------------- Resolution: Done Since we use 'vagrant status --machine-readable --no-color' we get back the following: {code} 1476770838,default,provider-name,virtualbox 1476770838,default,state,not_created 1476770838,default,state-human-short,not created 1476770838,default,state-human-long,The environment has not yet been created. Run `vagrant up` to\ncreate the environment. If a machine is not created%!(VAGRANT_COMMA) only the\ndefault provider will be shown. So if a provider is not listed%!(VAGRANT_COMMA)\nthen the machine is not created for that environment. {code} You'll notice one of the lines include not_created, so that's what we're keying off. And it works on both win and lin ;) > "not_created" not recognized as a vagrant state in master > --------------------------------------------------------- > > Key: JBIDE-23179 > URL: https://issues.jboss.org/browse/JBIDE-23179 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.2.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > > A vagrant machine in state not_created is not recognized at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23179) "not_created" not recognized as a vagrant state in master

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23179?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23179: -------------------------------- Summary: "not_created" not recognized as a vagrant state in master (was: "poweroff" not recognized as a vagrant state in master) > "not_created" not recognized as a vagrant state in master > --------------------------------------------------------- > > Key: JBIDE-23179 > URL: https://issues.jboss.org/browse/JBIDE-23179 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.2.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM1 > > > A vagrant machine in state not_created is not recognized at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3903: --------------------------------- [~xcoulon], thanks for the feedback! I've removed the reference to boot2docker, and reworked this point to address the Docker part: -------- (Optional) Install Docker individually to use Docker for Windows. Red Hat Development Suite includes Red Hat Container Development Kit, which includes the Docker tooling. To use the full version of Docker for WIndows outside Red Hat Development Suite, you must install Docker and test it before installing any Eclipse Docker tools. -------- Any thoughts? > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: docker > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Misha Ali > Fix For: 10.2.0.AM3 > > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Misha Ali edited comment on JBDS-3903 at 10/18/16 1:47 AM: ----------------------------------------------------------- [~xcoulon], thanks for the feedback! I've removed the reference to boot2docker, and reworked this point to address the Docker part: -------- (Optional) Install Docker individually to use Docker for Windows. Red Hat Development Suite includes Red Hat Container Development Kit, which includes the Docker tooling. To use the full version of Docker for WIndows outside Red Hat Development Suite, you must install Docker and test it before installing any Eclipse Docker tools. -------- Edit: Please use the same link as earlier to review the changes. Any thoughts? was (Author: mhusnain): [~xcoulon], thanks for the feedback! I've removed the reference to boot2docker, and reworked this point to address the Docker part: -------- (Optional) Install Docker individually to use Docker for Windows. Red Hat Development Suite includes Red Hat Container Development Kit, which includes the Docker tooling. To use the full version of Docker for WIndows outside Red Hat Development Suite, you must install Docker and test it before installing any Eclipse Docker tools. -------- Any thoughts? > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: docker > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Misha Ali > Fix For: 10.2.0.AM3 > > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23334) Base New and Noteworthy for 4.4.2.AM2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23334?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-23334. ------------------------------- Resolution: Done Nothing notable here! > Base New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23334 > URL: https://issues.jboss.org/browse/JBIDE-23334 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common, foundation, usage > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Base JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Base, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Base by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Base4.4.2.AM2 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Base for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4065) DevStudio 1.1 Installer unfriendly when 1.0 present

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4065?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-4065: ----------------------------------- [~mmalina] Yes, our sole criteria for whether to create a new server adapter is whether or not an adapter with the same folder exists. So basically, yes, the same Vagrantfile. This means a new cdk server adapter won't be created. > DevStudio 1.1 Installer unfriendly when 1.0 present > --------------------------------------------------- > > Key: JBDS-4065 > URL: https://issues.jboss.org/browse/JBDS-4065 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 10, DevSuite Installer 1.0 had been run > Reporter: Rick Wagner > Assignee: Rob Stryker > > When running the DevSuite 1.1 installer, DevStudio is not connected to the installed CDK. > Observations: > - All components removed before installation, does not help. (VirtualBox and Vagrant using Add/Remove programs, everything else directory-deleted, Environment variables cleaned). > - DevStudio says it can't start the Container Development Environment server. ('Failed to find Vagrant!' reads the error). If I open Launch Configuration, it lists the Main as "C:\HashiCorp\Vagrant\bin\vagrant.exe", which is not in the installation directory. > - It was noted that DevStudio marked itself 'completed' before Vagrant was installed. How does DevStudio know where Vagrant is? > - It's noted that DevStudio 'remembers' user settings (i.e. CDK registration user/password) from previous attempts. Where is this information kept? I must've missed something in cleanup. > - Tried full suite installation, then deleting DevStudio, then re-installing. (Hoping DevStudio would then find Vagrant in the right location, because it followed Vagrant's installation.) Result: No Container Development Environment server is present in 'server' view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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