[JBoss JIRA] (JBDS-3864) Why is the platform installer installing pscp when Cygwin openssh scp is also installed?
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3864?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3864:
--------------------------------
Story Points: 3
> Why is the platform installer installing pscp when Cygwin openssh scp is also installed?
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-3864
> URL: https://issues.jboss.org/browse/JBDS-3864
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Optional
> Fix For: 10.0.0.Alpha3
>
>
> Why does the platform installer install putty's pscp.ese when it also installs Cygwin's openssh which includes scp?
> A while back vagrant-service-manager had a dependency on pscp.exe for copying certificates, but I believe that was eliminated a while back. (around the time of the rename from adbinfo to service-manager).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3865) Platform installer should warn about known bad versions of Vagrant.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3865?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3865:
--------------------------------
Story Points: 2
> Platform installer should warn about known bad versions of Vagrant.
> -------------------------------------------------------------------
>
> Key: JBDS-3865
> URL: https://issues.jboss.org/browse/JBDS-3865
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit.
> Vagrant 1.8.1 installed
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.0.0.Alpha3
>
>
> The platform installer should flag versions of Vagrant (and possibly other software) that are known to be bad. There should possibly be a black list.
> Vagrant 1.8.0 and 1.8.1 have a bunch of bugs, so they aren't recommended for CDK.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3727) Installer fails with not normalized paths
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3727?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3727:
-----------------------------
> Installer fails with not normalized paths
> -----------------------------------------
>
> Key: JBDS-3727
> URL: https://issues.jboss.org/browse/JBDS-3727
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 10.0.0.Alpha3
>
>
> The installer accepts installation paths with the following format:
> {noformat}/home/jrichter/Downloads/xyz/../abdc/../temp/../temp{noformat}
> With such a path it fails immediately after the installation starts with the following exception:
> {noformat}java.io.FileNotFoundException: /home/jrichter/Downloads/xyz/../abdc/../temp/../temp/JBoss-EULA.html (No such file or directory)
> at java.io.FileOutputStream.open0(Native Method)
> at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
> at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:448)
> at java.lang.Thread.run(Thread.java:745){noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3727) Installer fails with not normalized paths
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3727?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3727:
--------------------------------
> Installer fails with not normalized paths
> -----------------------------------------
>
> Key: JBDS-3727
> URL: https://issues.jboss.org/browse/JBDS-3727
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 10.0.0.Alpha3
>
>
> The installer accepts installation paths with the following format:
> {noformat}/home/jrichter/Downloads/xyz/../abdc/../temp/../temp{noformat}
> With such a path it fails immediately after the installation starts with the following exception:
> {noformat}java.io.FileNotFoundException: /home/jrichter/Downloads/xyz/../abdc/../temp/../temp/JBoss-EULA.html (No such file or directory)
> at java.io.FileOutputStream.open0(Native Method)
> at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
> at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:448)
> at java.lang.Thread.run(Thread.java:745){noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3727) Installer fails with not normalized paths
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3727?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3727:
--------------------------------
Story Points: 2
Target Release: (was: 10.0.0.Alpha3)
> Installer fails with not normalized paths
> -----------------------------------------
>
> Key: JBDS-3727
> URL: https://issues.jboss.org/browse/JBDS-3727
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 10.0.0.Alpha3
>
>
> The installer accepts installation paths with the following format:
> {noformat}/home/jrichter/Downloads/xyz/../abdc/../temp/../temp{noformat}
> With such a path it fails immediately after the installation starts with the following exception:
> {noformat}java.io.FileNotFoundException: /home/jrichter/Downloads/xyz/../abdc/../temp/../temp/JBoss-EULA.html (No such file or directory)
> at java.io.FileOutputStream.open0(Native Method)
> at java.io.FileOutputStream.open(FileOutputStream.java:270)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
> at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
> at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:448)
> at java.lang.Thread.run(Thread.java:745){noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3865) Platform installer should warn about known bad versions of Vagrant.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3865?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3865:
--------------------------------
Sprint: devex #114 May 2017
> Platform installer should warn about known bad versions of Vagrant.
> -------------------------------------------------------------------
>
> Key: JBDS-3865
> URL: https://issues.jboss.org/browse/JBDS-3865
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit.
> Vagrant 1.8.1 installed
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.0.0.Alpha3
>
>
> The platform installer should flag versions of Vagrant (and possibly other software) that are known to be bad. There should possibly be a black list.
> Vagrant 1.8.0 and 1.8.1 have a bunch of bugs, so they aren't recommended for CDK.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months