[JBoss JIRA] (JBIDE-12656) org.jboss.tools.jst.css.test.jbide.SelectionLosingByPropertySheet_JBIDE4791 failure
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12656?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-12656.
-------------------------------
> org.jboss.tools.jst.css.test.jbide.SelectionLosingByPropertySheet_JBIDE4791 failure
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-12656
> URL: https://issues.jboss.org/browse/JBIDE-12656
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.0.0.Alpha2
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.Beta2
>
>
> {code}
> testSelectionLosingByPropertySheet(org.jboss.tools.jst.css.test.jbide.SelectionLosingByPropertySheet_JBIDE4791) Time elapsed: 21.54 sec <<< FAILURE!
> junit.framework.ComparisonFailure: expected:<red> but was:<null>
> at junit.framework.Assert.assertEquals(Assert.java:85)
> at junit.framework.Assert.assertEquals(Assert.java:91)
> at org.jboss.tools.jst.css.test.jbide.SelectionLosingByPropertySheet_JBIDE4791.testSelectionLosingByPropertySheet(SelectionLosingByPropertySheet_JBIDE4791.java:94)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBDS-3052) Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3052?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3052:
-----------------------------
Release Notes Docs Status: Not Yet Documented
Release Notes Text: Should document the fact that to enforce a multi-user install on Windows, the shared install folder must correctly be configured to be READ ONLY for all standard users.
> Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3052
> URL: https://issues.jboss.org/browse/JBDS-3052
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 8.0.0.Beta2
>
> 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)
> * dummy (a standard user)
> * kid (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.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBDS-3052) Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3052?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3052:
-----------------------------
Issue Type: Story (was: Feature Request)
Workflow: classic default workflow (was: CDW v1)
Status: Open (was: New)
> Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3052
> URL: https://issues.jboss.org/browse/JBDS-3052
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 8.0.0.Beta2
>
> 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)
> * dummy (a standard user)
> * kid (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.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBDS-3052) Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3052?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3052:
-----------------------------
Summary: Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only (was: Shared install on Windows doesn't use private folders for updates/workspace)
Fix Version/s: 8.0.0.Beta2
Assignee: Nick Boldt
> Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3052
> URL: https://issues.jboss.org/browse/JBDS-3052
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 8.0.0.Beta2
>
> 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)
> * dummy (a standard user)
> * kid (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.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17148) Improvements needed (regarding caching) in the URLTransport* API
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17148?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-17148:
-------------------------------------
Please provide steps to verify
> Improvements needed (regarding caching) in the URLTransport* API
> ----------------------------------------------------------------
>
> Key: JBIDE-17148
> URL: https://issues.jboss.org/browse/JBIDE-17148
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.2.0.Beta1
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.2.0.Beta2
>
>
> There are a few things I'd like to see improved in the URL Transport API, wrt caching.
> Currently :
> * all files are downloaded and cached under <workspace>/.metadata/.plugins/org.jboss.tools.foundation.core/ECF_REMOTE_CACHE, using a cryptic name
> * Cache doesn't survive JVM restart
> What I need/expect :
> * ability to set custom cache folder
> * store files under <cache.folder>/requested.url. eg. : if I request https://foo.bar.org:8080/some/location/file.txt, it'll be stored under <workspace>/.metadata/.plugins/my.plugin/cache/http_foo.bar.org_8080/some/location/file.txt
> * restarting the IDE will be able to read the cached file
> Currently URLTransportCache is a singleton. We could change that and add the cache location as a constructor argument, have a URLTransportCache.DEFAULT instance, used by URLTransportUtility and probably override
> {quote}
> public File getCachedFileForURL(String url, String displayName, int lifespan, IProgressMonitor monitor)
> {quote}
> with
> {quote}
> public File getCachedFileForURL(String url, String displayName, URLTransportCache transportCache, IProgressMonitor monitor)
> {quote}
> Or if you have any better idea, be my guest :-)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBDS-3052) Shared install on Windows doesn't use private folders for updates/workspace
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3052?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3052:
-----------------------------
Attachment: w-shared-install-jbdevstudio-security-permissions-remove-authenticated-users.png
jbds8b2-windows8.1-shared-install-readonly-now-installs-into-users-kid-.eclipse-folder.png
If I remove the Authenticated Users option
{quote}right-click a folder > Properties > Security tab > Advanced > Disable Inheritance > Convert > Select "Authenticated Users" > Remove > OK{quote}
Then I get this:
!w-shared-install-jbdevstudio-security-permissions-remove-authenticated-users.png!
And now, when I try to launch the shared JBDS, the suggested workspace folder is *C:\users\kid\workspace*, as it should be.
If I attempt to install new features from Central, I get new content in the child user's .eclipse folder:
!jbds8b2-windows8.1-shared-install-readonly-now-installs-into-users-kid-.eclipse-folder.png!
> Shared install on Windows doesn't use private folders for updates/workspace
> ---------------------------------------------------------------------------
>
> Key: JBDS-3052
> URL: https://issues.jboss.org/browse/JBDS-3052
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Nick Boldt
> 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)
> * dummy (a standard user)
> * kid (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.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBDS-3052) Shared install on Windows doesn't use private folders for updates/workspace
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3052?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3052:
-----------------------------
Attachment: w-shared-install-jbdevstudio-security-permissions.png
Looks like the problem might be the way the default permissions are set up on the folder:
Authenticated Users get full Write permission, while Users are restricted to only Read/Execute.
So perhaps if an administrator correctly sets locked-down permissions on the shared folder (that is, installs to a dir which is NOT open to Authenticated Users getting Write permission) Eclipse may correctly be installed for multi-user confiuration.
> Shared install on Windows doesn't use private folders for updates/workspace
> ---------------------------------------------------------------------------
>
> Key: JBDS-3052
> URL: https://issues.jboss.org/browse/JBDS-3052
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Nick Boldt
> Attachments: jbds8b2-windows8.1-child-user-private-install-updated-via-central.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.png, win81pro-details.png
>
>
> To test the user experience on Windows, I created three accounts:
> * nboldt (my own admin user)
> * dummy (a standard user)
> * kid (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.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBDS-3052) Shared install on Windows doesn't use private folders for updates/workspace
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3052?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3052 at 5/29/14 10:45 AM:
------------------------------------------------------------
Looks like the problem might be the way the default permissions are set up on the folder:
Authenticated Users get full Write permission, while Users are restricted to only Read/Execute:
!w-shared-install-jbdevstudio-security-permissions.png!
So perhaps if an administrator correctly sets locked-down permissions on the shared folder (that is, installs to a dir which is NOT open to Authenticated Users getting Write permission) Eclipse may correctly be installed for multi-user confiuration.
was (Author: nickboldt):
Looks like the problem might be the way the default permissions are set up on the folder:
Authenticated Users get full Write permission, while Users are restricted to only Read/Execute.
So perhaps if an administrator correctly sets locked-down permissions on the shared folder (that is, installs to a dir which is NOT open to Authenticated Users getting Write permission) Eclipse may correctly be installed for multi-user confiuration.
> Shared install on Windows doesn't use private folders for updates/workspace
> ---------------------------------------------------------------------------
>
> Key: JBDS-3052
> URL: https://issues.jboss.org/browse/JBDS-3052
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Nick Boldt
> Attachments: jbds8b2-windows8.1-child-user-private-install-updated-via-central.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.png, win81pro-details.png
>
>
> To test the user experience on Windows, I created three accounts:
> * nboldt (my own admin user)
> * dummy (a standard user)
> * kid (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.2.3#6260)
11 years, 10 months