[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools
by Josephine Qian (JIRA)
[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ]
Josephine Qian updated JBDS-3635:
---------------------------------
Attachment: Technologies 5.pdf
> Add the ability to detect/select existing dependencies/tools
> ------------------------------------------------------------
>
> Key: JBDS-3635
> URL: https://issues.jboss.org/browse/JBDS-3635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
> Fix For: 9.1.0.CR1
>
> Attachments: pdkinstaller.png, Technologies 5.pdf
>
>
> It would be great if the installer allowed the user to use some of the required tools they have already installed.
> The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc.
> The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter):
> !pdkinstaller.png|thumbnail!
> [~dgolovin] & [~crobson], what's your opinion on this?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools
by Josephine Qian (JIRA)
[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ]
Josephine Qian commented on JBDS-3635:
--------------------------------------
The design has been agreed within the team. For the reference: [^Technologies 5.pdf]
> Add the ability to detect/select existing dependencies/tools
> ------------------------------------------------------------
>
> Key: JBDS-3635
> URL: https://issues.jboss.org/browse/JBDS-3635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
> Fix For: 9.1.0.CR1
>
> Attachments: pdkinstaller.png, Technologies 5.pdf
>
>
> It would be great if the installer allowed the user to use some of the required tools they have already installed.
> The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc.
> The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter):
> !pdkinstaller.png|thumbnail!
> [~dgolovin] & [~crobson], what's your opinion on this?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3636) Installer - If the installation encounters a box download issue, the install fails, and the user must manually cleanup before retrying
by Josephine Qian (JIRA)
[ https://issues.jboss.org/browse/JBDS-3636?page=com.atlassian.jira.plugin.... ]
Josephine Qian edited comment on JBDS-3636 at 3/14/16 4:43 PM:
---------------------------------------------------------------
Sad to hear that users have to manually cleanup the install. Is there anything we could do to reduce their pain?
Regardless of that, I think we could at least present the error on the main screen, not just the pop over notification. We could achieve that by rendering the progress bar red and showing a short error message. Please see the attachment for recommnendation[^installing.png]
Note:
The progress bar with textual information can be found in PatternFly: https://www.patternfly.org/widgets/#progress
was (Author: joqian):
Sad to hear that users have to manually cleanup the install. Is there anything we could do to reduce their pain?
Regardless of that, I think we could at least present the error on the main screen, not just the pop over notification. We could achieve that by rendering the progress bar red and showing a short error message.
Note:
The progress bar with textual information can be found in PatternFly: https://www.patternfly.org/widgets/#progress
> Installer - If the installation encounters a box download issue, the install fails, and the user must manually cleanup before retrying
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3636
> URL: https://issues.jboss.org/browse/JBDS-3636
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Len DiMaggio
> Assignee: Joshua Wilson
> Labels: havoc, ui
> Fix For: 9.1.0.CR1
>
> Attachments: Download.png, installing.png
>
>
> See the attached screenshot - The installation in question failed due to a download issue with the box file. Only path forward for the user was to manually abort the install, manually cleanup the install, and retry.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3636) Installer - If the installation encounters a box download issue, the install fails, and the user must manually cleanup before retrying
by Josephine Qian (JIRA)
[ https://issues.jboss.org/browse/JBDS-3636?page=com.atlassian.jira.plugin.... ]
Josephine Qian commented on JBDS-3636:
--------------------------------------
Sad to hear that users have to manually cleanup the install. Is there anything we could do to reduce their pain?
Regardless of that, I think we could at least present the error on the main screen, not just the pop over notification. We could achieve that by rendering the progress bar red and showing a short error message.
Note:
The progress bar with textual information can be found in PatternFly: https://www.patternfly.org/widgets/#progress
> Installer - If the installation encounters a box download issue, the install fails, and the user must manually cleanup before retrying
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3636
> URL: https://issues.jboss.org/browse/JBDS-3636
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Len DiMaggio
> Assignee: Joshua Wilson
> Labels: havoc, ui
> Fix For: 9.1.0.CR1
>
> Attachments: Download.png, installing.png
>
>
> See the attached screenshot - The installation in question failed due to a download issue with the box file. Only path forward for the user was to manually abort the install, manually cleanup the install, and retry.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ERT-83) com.google.gson is required but not named in any feature.xml [EBZ#487768]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-83?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan reassigned ERT-83:
-------------------------------
Assignee: Victor Rubezhny
> com.google.gson is required but not named in any feature.xml [EBZ#487768]
> -------------------------------------------------------------------------
>
> Key: ERT-83
> URL: https://issues.jboss.org/browse/ERT-83
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Victor Rubezhny
> Labels: General, bzira
>
> The bundle org.eclipse.wst.jsdt.js.npm had a dependency on com.google.gson, but that google bundle from Orbit is not mentioned by the enclosing feature org.eclipse.wst.jsdt.nodejs.feature.
> This was found by doing a P2 mirror operation of the WTP repository and finding that com.google.gson was not brought along for the ride.
> Though an install from the WTP repository will find the bundle and work, it's important for the feature to name the dependency also so that in the future if a patch is required on com.google.gson, we can create a feature patch to insert a newer version. This will be appreciated by those doing support in the future.
> It will also mean that a mirror operation will bring along the proper set of dependencies.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years