[JBoss JIRA] (JBDS-4336) Promote MSI as preferable packaging for components available for installation on windows
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4336?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4336:
--------------------------------
Epic Status: Done (was: To Do)
> Promote MSI as preferable packaging for components available for installation on windows
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-4336
> URL: https://issues.jboss.org/browse/JBDS-4336
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.3.0.AM2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 11.x
>
>
> MSI if preferable packaging for components available for installation on Windows. Installer should provide:
> 1. Generic configurable installer for MSI packages
> 2. Document steps how to include MSI packed component into devsuite
> 3. Document steps how to build MSI installers using WIX Toolset
> 4. Detection for MSI components based om windows metadata
> 5. Uninstaller support
> 6. Update/replacement support for conflicting versions
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBDS-4336) Promote MSI as preferable packaging for components available for installation on windows
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4336?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4336:
--------------------------------
Summary: Promote MSI as preferable packaging for components available for installation on windows (was: Promote MSI installer as preferable packaging for components available for installation on windows)
> Promote MSI as preferable packaging for components available for installation on windows
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-4336
> URL: https://issues.jboss.org/browse/JBDS-4336
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.3.0.AM2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 11.x
>
>
> MSI if preferable packaging for components available for installation on Windows. Installer should provide:
> 1. Generic configurable installer for MSI packages
> 2. Document steps how to include MSI packed component into devsuite
> 3. Document steps how to build MSI installers using WIX Toolset
> 4. Detection for MSI components based om windows metadata
> 5. Uninstaller support
> 6. Update/replacement support for conflicting versions
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3627:
--------------------------------
Epic Status: Done
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 11.2.0.AM3
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689.
> DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification:
> 1. that provided credentials are valid;
> 2. that required T&C's are signed.
> There are two major use cases for developers installing DevSuite using Installer:
> 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf;
> 2. Shared installer - when someone share installer with developers without account.
> There two kind of users involved in those scenarios above:
> 1. New users that must go through registration process;
> 2. Registered users.
> *Direct download*
> For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation.
> For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579.
> So far there are two kind of problems:
> 1. Users can login and download DevSuite installer, but cannot use the same credentials to install;
> 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used
> *Shared Download*
> In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation.
> Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-3627.
-------------------------------
Resolution: Done
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 11.2.0.AM3
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689.
> DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification:
> 1. that provided credentials are valid;
> 2. that required T&C's are signed.
> There are two major use cases for developers installing DevSuite using Installer:
> 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf;
> 2. Shared installer - when someone share installer with developers without account.
> There two kind of users involved in those scenarios above:
> 1. New users that must go through registration process;
> 2. Registered users.
> *Direct download*
> For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation.
> For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579.
> So far there are two kind of problems:
> 1. Users can login and download DevSuite installer, but cannot use the same credentials to install;
> 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used
> *Shared Download*
> In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation.
> Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months