[JBoss JIRA] (TOOLSDOC-536) Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-536?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-536:
-------------------------------------
Component/s: Installation Guide
> Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-536
> URL: https://issues.jboss.org/browse/TOOLSDOC-536
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Story
> Components: Installation Guide
> Affects Versions: 4.2.0.Final
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Attachments: jbds8b2-windows8.1-child-user-private-install-updated-via-central.png, jbds8b2-windows8.1-shared-install-readonly-now-installs-into-users-kid-.eclipse-folder.png, jbds8b2-windows8.1-standard-user-install-error-in-central.png, jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png, jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png, w-shared-install-jbdevstudio-security-permissions-remove-authenticated-users.png, w-shared-install-jbdevstudio-security-permissions.png, win81pro-details.png
>
>
> To test the user experience on Windows, I created three accounts:
> * nboldt (my own admin user)
> * {color:orange}*dummy*{color} (a standard user)
> * {color:green}*kid*{color} (a child user, which is a standard user but with Family Safety logging - http://windows.microsoft.com/en-ca/windows-8/create-child-account )
> Both the child and standard users were able to install JBDS into their own home folders and perform an installation from Central:
> !jbds8b2-windows8.1-child-user-private-install-updated-via-central.png!
> !jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png!
> ------
> However, there are problems when using an Admin user-installed shared install folder for JBDS.
> Steps to repro:
> *As nboldt / admin user*
> * install JBDS 8.0.0.Beta2 (B104) into W:\shared-install\jbdevstudio (using default ownership/permissions)
> *As dummy / standard user*
> * Log in
> * Launch the shared JBDS
> * Install something from Central
> !jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png!
> *PROBLEM*: standard user should not be able to install new features into the shared install folder
> *As kid / child user*
> * Log in
> * Launch the shared JBDS
> * Noted that the suggested path for workspace was the one last used by *dummy user*, to which that user doesn't have read permission
> !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png!
> !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png!
> !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png!
> *PROBLEM*: should default to current user's home dir, not another user's previous workspace selection
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (TOOLSDOC-536) Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-536?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-536:
-------------------------------------
Affects Version/s: 4.2.0.Final
> Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-536
> URL: https://issues.jboss.org/browse/TOOLSDOC-536
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Story
> Components: Installation Guide
> Affects Versions: 4.2.0.Final
> Reporter: Nick Boldt
> Assignee: Michelle Murray
> Attachments: jbds8b2-windows8.1-child-user-private-install-updated-via-central.png, jbds8b2-windows8.1-shared-install-readonly-now-installs-into-users-kid-.eclipse-folder.png, jbds8b2-windows8.1-standard-user-install-error-in-central.png, jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png, jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png, w-shared-install-jbdevstudio-security-permissions-remove-authenticated-users.png, w-shared-install-jbdevstudio-security-permissions.png, win81pro-details.png
>
>
> To test the user experience on Windows, I created three accounts:
> * nboldt (my own admin user)
> * {color:orange}*dummy*{color} (a standard user)
> * {color:green}*kid*{color} (a child user, which is a standard user but with Family Safety logging - http://windows.microsoft.com/en-ca/windows-8/create-child-account )
> Both the child and standard users were able to install JBDS into their own home folders and perform an installation from Central:
> !jbds8b2-windows8.1-child-user-private-install-updated-via-central.png!
> !jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png!
> ------
> However, there are problems when using an Admin user-installed shared install folder for JBDS.
> Steps to repro:
> *As nboldt / admin user*
> * install JBDS 8.0.0.Beta2 (B104) into W:\shared-install\jbdevstudio (using default ownership/permissions)
> *As dummy / standard user*
> * Log in
> * Launch the shared JBDS
> * Install something from Central
> !jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png!
> *PROBLEM*: standard user should not be able to install new features into the shared install folder
> *As kid / child user*
> * Log in
> * Launch the shared JBDS
> * Noted that the suggested path for workspace was the one last used by *dummy user*, to which that user doesn't have read permission
> !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png!
> !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png!
> !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png!
> *PROBLEM*: should default to current user's home dir, not another user's previous workspace selection
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (TOOLSDOC-378) Documentation on adding EAP to JBDS 7 is not as effective as documentation for JBDS 6
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-378?page=com.atlassian.jira.plug... ]
Michelle Murray resolved TOOLSDOC-378.
--------------------------------------
Resolution: Out of Date
> Documentation on adding EAP to JBDS 7 is not as effective as documentation for JBDS 6
> -------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-378
> URL: https://issues.jboss.org/browse/TOOLSDOC-378
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: Getting Started Guide, Installation Guide
> Affects Versions: 4.1.0
> Reporter: Nick Boldt
> Assignee: Michelle Murray
>
> For JBDS 6 we had this, complete with screenshots and example content:
> https://access.redhat.com/site/documentation/en-US/JBoss_Developer_Studio...
> Now, we have this:
> {code:title=https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Developer_Studio/7.0/html-single/Getting_Started_Guide/index.html#Set_Up_a_Runtime_Server_Using_Server_Manager}
> 5.2. Set Up a Server Using Runtime Detection
> Servers can be set up from within the Java EE Web Project wizard. But for the purposes of exploring JBoss Developer Studio the procedure below sets up the server first.
> Procedure 5.2. Set Up a Server Using Runtime Detection
> Click Window→Preferences, expand JBoss Tools and select JBoss Tools Runtime Detection.
> Click Add.
> Select the directory containing the JBoss Enterprise Application Platform 6.0 or JBoss Enterprise Application Platform 6.1 installation and click OK. The directory is now scanned for application servers and JBoss Enterprise Application Platform 6.x found.
> To create a server for JBoss Enterprise Application Platform 6.x, ensure the jboss-eap-6.x check box is selected and click OK.
> Click Apply and click OK to close the Preferences window. The server is listed in the Servers tab.
> The server is initially shown in stopped mode. To start the server, right-click jboss-eap-6.x and click Start. After a short pause, the view switches to the Console tab and shows the startup output of the server.
> {code}
> AND we have this, which is more verbose but fails to mention any EAP 6.x specific examples.
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope...
> Additionally, the html anchor "Set_Up_a_Runtime_Server_Using_Server_Manager" for "5.2 Set Up a Server Using Runtime Detection" doesn't match the content.
> https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope...
> -----
> Could the content in both places be updated/merged to equally complete, and could screenshots be added too?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months