[JBoss JIRA] (JBDS-3812) Target folder input looks weird
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBDS-3812?page=com.atlassian.jira.plugin.... ]
Joshua Wilson updated JBDS-3812:
--------------------------------
Affects Version/s: 10.0.0.Alpha1
(was: 9.1.0.CR1)
> Target folder input looks weird
> -------------------------------
>
> Key: JBDS-3812
> URL: https://issues.jboss.org/browse/JBDS-3812
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.0.0.Alpha1
> Reporter: Jan Richter
> Assignee: Joshua Wilson
> Labels: havoc, ui
> Attachments: selected.png, unselected.png
>
>
> There are a few visual issues with the target folder input group that make it look really weird:
> - When not focused, there is no real border around the input box, just a little line on the bottom
> - The Browse button is shoved right on top of the input field - when the field is focused, its border is hidden under the button on the right
> - The input field should probably be auto-focused
> - When the validation message shows an error, it has a red icon with black text
> - The path with spaces warning has black text - plus since this path is not allowed, it should show as error, not a warning
> - The message that folder will be created looks exactly like a warning, it should be styled as info (no orange text and icon)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3831) A little typo in detection info
by Jan Richter (JIRA)
Jan Richter created JBDS-3831:
---------------------------------
Summary: A little typo in detection info
Key: JBDS-3831
URL: https://issues.jboss.org/browse/JBDS-3831
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Jan Richter
Assignee: Joshua Wilson
Priority: Trivial
When a different version than recommended is found, it says "Newer/Older that recommended!" instead of "than recommended!"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3804) Installer: exe distribution has wrong metadata
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3804?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-3804.
----------------------------
[~jrichter1] confirms this is already fixed so closing.
> Installer: exe distribution has wrong metadata
> ----------------------------------------------
>
> Key: JBDS-3804
> URL: https://issues.jboss.org/browse/JBDS-3804
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Reporter: Pavol Pitonak
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 9.1.0.GA
>
> Attachments: installer_metadata.png
>
>
> # download distribution from http://machydra.tpb.lab.eng.brq.redhat.com:8080/view/Developer%20Tooling/... (link to smaller version, bundled installer has the same problem)
> # right-click on downloaded exe file, select _Properties_, switch to _Details_ tab
> OR
> # clone git repo
> # npm install
> # npm run package-simple
> # right-click on _dist/win/DeveloperPlatformInstaller-win32-x64/DeveloperPlatformInstaller.exe_ and select _Properties_, switch to _Details_ tab
> # right-click on _dist/win/DeveloperPlatformInstaller-win32-x64-0.0.2.exe_ and select _Properties_, switch to _Details_ tab
> result:
> * electron-generate creates exe with correct metadata
> * distribution exe contains wrong metadata (e.g. copyright to Igor Pavlov)
> * *needs to be fixed before we sign the binary*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (TOOLSDOC-709) JBDS 9.1 GA: Document a use case for Forge Tooling
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-709?page=com.atlassian.jira.plug... ]
Pavol Srna resolved TOOLSDOC-709.
---------------------------------
Resolution: Done
The doc looks ok.
> JBDS 9.1 GA: Document a use case for Forge Tooling
> --------------------------------------------------
>
> Key: TOOLSDOC-709
> URL: https://issues.jboss.org/browse/TOOLSDOC-709
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Components: General documentation issues
> Affects Versions: 9.1 GA
> Reporter: Misha Ali
> Assignee: Supriya Bharadwaj
> Labels: Forge
> Fix For: 9.1 GA
>
>
> Document a use case for Forge tooling.
> 1. Draft a potential use case for what users may want to do with forge.
> 2. Get review on use case idea from a relevant SME or QE person
> 3. Write an intro and flesh out the use case with relevant screenshots
> 4. Get QE review
> 5. Create upstream and downstream versions of approved content.
> a. Add CSP version to customer portal
> b. Send Misha upstream version
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3830) Vagrant detection does not work if its installation path has spaces
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3830?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3830:
------------------------------
Description:
I have installed Vagrant 1.8.1 into c:\Hashi Corp\Vagrant\
On the confirmation page it says there is an existing vagrant installation, but it provides no info as to what version or where it is located.
Clicking install -> vagrant starts downloading, the existing installation is not used. Then the installation fails because a newer version is already installed.
was:
I have installed Vagrant into c:\Hashi Corp\Vagrant\
On the confirmation page it says there is an existing vagrant installation, but it provides no info as to what version or where it is located.
Clicking install -> vagrant starts downloading, the existing installation is not used.
> Vagrant detection does not work if its installation path has spaces
> -------------------------------------------------------------------
>
> Key: JBDS-3830
> URL: https://issues.jboss.org/browse/JBDS-3830
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
>
> I have installed Vagrant 1.8.1 into c:\Hashi Corp\Vagrant\
> On the confirmation page it says there is an existing vagrant installation, but it provides no info as to what version or where it is located.
> Clicking install -> vagrant starts downloading, the existing installation is not used. Then the installation fails because a newer version is already installed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3830) Vagrant detection does not work if its installation path has spaces
by Jan Richter (JIRA)
Jan Richter created JBDS-3830:
---------------------------------
Summary: Vagrant detection does not work if its installation path has spaces
Key: JBDS-3830
URL: https://issues.jboss.org/browse/JBDS-3830
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Jan Richter
Assignee: Denis Golovin
I have installed Vagrant into c:\Hashi Corp\Vagrant\
On the confirmation page it says there is an existing vagrant installation, but it provides no info as to what version or where it is located.
Clicking install -> vagrant starts downloading, the existing installation is not used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years