[JBoss JIRA] (JBDS-3701) Add check for an existing Java to find if it is JRE or JDK
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3701?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3701:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> Add check for an existing Java to find if it is JRE or JDK
> ----------------------------------------------------------
>
> Key: JBDS-3701
> URL: https://issues.jboss.org/browse/JBDS-3701
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 11.0.0.AM2
>
>
> JBDS will run on both, but in order to develop something the user needs a JDK. The detection/selection will allow using JRE distribution of Java without even a warning. We should find out what kind of Java the user has selected and at least display a warning if it is not JDK (or just not allow JRE).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 12 months
[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3841:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> Installer Sets Path for Wrong User
> ----------------------------------
>
> Key: JBDS-3841
> URL: https://issues.jboss.org/browse/JBDS-3841
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.GA
> Environment: Windows 10
> Reporter: Thomas Mäder
> Assignee: Denis Golovin
> Priority: Critical
> Labels: user-docs
> Fix For: 11.0.0.AM2
>
>
> When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 12 months
[JBoss JIRA] (JBDS-4121) Run DevSuite Installer with Elevated privileges on Mac OSX
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4121?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4121:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> Run DevSuite Installer with Elevated privileges on Mac OSX
> ----------------------------------------------------------
>
> Key: JBDS-4121
> URL: https://issues.jboss.org/browse/JBDS-4121
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.2.0.AM2
> Environment: Mac OS X
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 11.0.0.AM2
>
> Attachments: DevSuite.zip
>
>
> During installation PATH environment variable should be updated. For example to make permanent changes for PATH variable /etc/paths file should be modified and that requires administrative privileges.
> For Alpha release we could be running installer with sudo
> {code}sudo open DevSuite.app{code}
> Another option to investigate is using AppleScript and run the same shell script above with elevated privileges like this
> {code}do shell script «open DevSuite.app» with administrator privileges{code}
> that would trigger standard UI Dialog requesting user login/password with administrative privileges. This should be included int DevSuite.app package configuration after it is assembled by electron packages.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 12 months
[JBoss JIRA] (JBDS-4430) EAP is not added to runtime locations
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4430?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4430:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> EAP is not added to runtime locations
> -------------------------------------
>
> Key: JBDS-4430
> URL: https://issues.jboss.org/browse/JBDS-4430
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.0.0.AM1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 11.0.0.AM2
>
>
> The event handler responsible for adding EAP to devstudio runtime locations gets called immediately after the main installation, no matter what state devstudio is in. Hence, EAP is not usually added to runtime_locations.properties.
> On windows, runtime detection can still somehow get past this and finds EAP on its own. But on mac it doesn't. Plus the location of runtime_locations.properties file on mac is different to other platforms (needs update in the code).
> And btw. it could use some logging as well.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 12 months
[JBoss JIRA] (JBDS-3868) Document (and check) required disk space before beginning install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3868?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3868:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> Document (and check) required disk space before beginning install
> -----------------------------------------------------------------
>
> Key: JBDS-3868
> URL: https://issues.jboss.org/browse/JBDS-3868
> Project: Red Hat JBoss 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: Minor
> Labels: ui
> Fix For: 11.0.0.AM2
>
>
> The installer and it's documentation should indicate the minimum required disk space before beginning the download and installation process.
> Between temporary files, and download/installs going on in parallel. I'm guessing at least 10-15 GB free is needed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 12 months
[JBoss JIRA] (JBDS-4330) GPG Signature verification for .json and .js files
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4330?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4330:
-----------------------------
Fix Version/s: 11.0.0.AM2
(was: 11.0.0.AM1)
Slip to AM2
> GPG Signature verification for .json and .js files
> --------------------------------------------------
>
> Key: JBDS-4330
> URL: https://issues.jboss.org/browse/JBDS-4330
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.0.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 11.0.0.AM2
>
>
> To allow loading remote configuration or even java script modules there should be a way to confirm origin of downloaded file to prevent 'man in the middle attacks'. Files loaded from remote location should bear GPG signature that installer should verify before proceeding with loaded file.
> This should be possible with https://github.com/openpgpjs/openpgpjs using https://openpgpjs.org/openpgpjs/doc/index.html using 'Create and verify detached signatures'.
> The Idea is to sign .json of .js file with GPG and then download it ad separate json/js code from the signature, verify it and then proceed with loading .json or js module form string.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 12 months