[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
[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
[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
[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
[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
[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