[JBoss JIRA] (JBDS-3834) Install fail - what next?
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3834?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3834:
--------------------------------
Story Points: 13
> Install fail - what next?
> -------------------------
>
> Key: JBDS-3834
> URL: https://issues.jboss.org/browse/JBDS-3834
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.1.0.GA
>
> Attachments: error.PNG, fail_install.PNG
>
>
> Testing the Installer a bit more and I realize this is currently tech preview but when one (or more) components fail, there is no next step for users. There is no cancel or quit button to exit the failed install, nor is there a retry for the failed component, nor any error message at all. As a user, I'd be confused about what I should do next at this stage. I think this might be worth looking into with UX for the 9.1 GA++ release.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-20362) Extracting of a download runtime is slow on Mac
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20362?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20362:
-------------------------------------
I've opened an upstream bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=499791
> 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
[JBoss JIRA] (JBIDE-20362) Extracting of a download runtime is slow on Mac
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20362?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20362:
-------------------------------------
I've made an example project which clearly demonstrates the speed difference, even on linux. You're not crazy martin ;)
Without setTaskName, it runs in 44 seconds. (300k iterations)
With setTaskName, it runs in 2 minutes, 23 seconds.
The bug is real ;)
> 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
[JBoss JIRA] (JBDS-4003) Update OC Origin to 1.2.0
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4003?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4003:
--------------------------------------
It should work. But testing it is always a good idea. cc: [~ldimaggio], [~mlabuda], [~mmalina]
> Update OC Origin to 1.2.0
> -------------------------
>
> Key: JBDS-4003
> URL: https://issues.jboss.org/browse/JBDS-4003
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.1.0.GA
>
>
> OC Origin used in DevSuite Installer should be updated to 1.2.0 to be in synch with one installed by vagrant service-manager install-cli command.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3862) Platform installer failed to detect existing Cygwin install with ssh and sftp
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3862?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-3862.
---------------------------------
Resolution: Done
> Platform installer failed to detect existing Cygwin install with ssh and sftp
> -----------------------------------------------------------------------------
>
> Key: JBDS-3862
> URL: https://issues.jboss.org/browse/JBDS-3862
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit,
> Cygwin 2.5.1 already installed in the detault location C:\cygwin.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Attachments: screenshot-1.png
>
>
> The installer did not detect the existing Cygwin install in C:\Cygwin.
> What test is used to determine if Cygwin is already installed?
> !screenshot-1.png!
> Installer uses {code}cygcheck -c cygwin openssh rsync{code} to veify cygwin installed and ssh, sftp and rsync are installed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months