[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 Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3052?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3052:
--------------------------------------
Fix Version/s: 8.0.0.CR1
(was: 8.0.0.Beta3)
> 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.CR1
>
> 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.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBDS-3095) Ensure JBT Early Access TP is updated when Beta3 is released (was: In JBDS 8.0.beta3, mylyn is listed as "beta2")
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3095?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-3095.
----------------------------
Resolution: Done
See https://issues.jboss.org/browse/JBIDE-17826?focusedCommentId=12986774&pag... for PRs which affect this solution.
> Ensure JBT Early Access TP is updated when Beta3 is released (was: In JBDS 8.0.beta3, mylyn is listed as "beta2")
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3095
> URL: https://issues.jboss.org/browse/JBDS-3095
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, discovery
> Affects Versions: 8.0.0.Beta3
> Environment: jboss-devstudio-8.0.0.Beta3-v20140712-0200-B178-installer-eap.jar
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/8.0.0.Beta3a/devstudio-directory.xml
> -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/8.0.0.Beta3a/
> -Djboss.discovery.earlyaccess.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/8.0.0.Beta3a/
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 8.0.0.CR1
>
> Attachments: o.j.t.common.mylyn-beta2-in-beta3.png
>
>
> In JBDS 8.0.beta3, the Mylyn plugin is listed as "beta2"
> JBoss Tools Common - Mylyn 3.6.0.Beta2-v20140612-0000-B39/RHDS/discovery/development/8.0.0.Beta3a/
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBDS-3094) Ensure JBT Central TP is updated when Beta3 is released (was: In JBDS 8.0.beta3, arquillian is listed as "beta2")
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3094?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen closed JBDS-3094.
-------------------------------------
Resolution: Duplicate Issue
> Ensure JBT Central TP is updated when Beta3 is released (was: In JBDS 8.0.beta3, arquillian is listed as "beta2")
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3094
> URL: https://issues.jboss.org/browse/JBDS-3094
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, discovery
> Affects Versions: 8.0.0.Beta3
> Environment: jboss-devstudio-8.0.0.Beta3-v20140712-0200-B178-installer-eap.jar
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/8.0.0.Beta3a/devstudio-directory.xml
> -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/8.0.0.Beta3a/
> -Djboss.discovery.earlyaccess.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/8.0.0.Beta3a/
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Fix For: 8.0.0.Beta3
>
> Attachments: arquillian-beta2-in-beta3.png
>
>
> Installing Arquillian support in beta3 - the plugin is listed as "beta2":
> Arquillian support (Experimental) 1.1.1.Beta2-v20140613-0222-B55
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBDS-3095) Ensure JBT Early Access TP is updated when Beta3 is released (was: In JBDS 8.0.beta3, mylyn is listed as "beta2")
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3095?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3095:
--------------------------------------
Priority: Blocker (was: Major)
> Ensure JBT Early Access TP is updated when Beta3 is released (was: In JBDS 8.0.beta3, mylyn is listed as "beta2")
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3095
> URL: https://issues.jboss.org/browse/JBDS-3095
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, discovery
> Affects Versions: 8.0.0.Beta3
> Environment: jboss-devstudio-8.0.0.Beta3-v20140712-0200-B178-installer-eap.jar
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/8.0.0.Beta3a/devstudio-directory.xml
> -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/8.0.0.Beta3a/
> -Djboss.discovery.earlyaccess.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/8.0.0.Beta3a/
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 8.0.0.CR1
>
> Attachments: o.j.t.common.mylyn-beta2-in-beta3.png
>
>
> In JBDS 8.0.beta3, the Mylyn plugin is listed as "beta2"
> JBoss Tools Common - Mylyn 3.6.0.Beta2-v20140612-0000-B39/RHDS/discovery/development/8.0.0.Beta3a/
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBDS-3095) Ensure JBT Early Access TP is updated when Beta3 is released (was: In JBDS 8.0.beta3, mylyn is listed as "beta2")
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3095?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3095:
--------------------------------------
Fix Version/s: 8.0.0.CR1
(was: 8.0.0.Beta3)
> Ensure JBT Early Access TP is updated when Beta3 is released (was: In JBDS 8.0.beta3, mylyn is listed as "beta2")
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3095
> URL: https://issues.jboss.org/browse/JBDS-3095
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, discovery
> Affects Versions: 8.0.0.Beta3
> Environment: jboss-devstudio-8.0.0.Beta3-v20140712-0200-B178-installer-eap.jar
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/8.0.0.Beta3a/devstudio-directory.xml
> -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/8.0.0.Beta3a/
> -Djboss.discovery.earlyaccess.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/8.0.0.Beta3a/
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Fix For: 8.0.0.CR1
>
> Attachments: o.j.t.common.mylyn-beta2-in-beta3.png
>
>
> In JBDS 8.0.beta3, the Mylyn plugin is listed as "beta2"
> JBoss Tools Common - Mylyn 3.6.0.Beta2-v20140612-0000-B39/RHDS/discovery/development/8.0.0.Beta3a/
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17947) Java Model Exception occurs while typing
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17947?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-17947:
---------------------------------------
[~rrabara],
thansk for the video, but I could not reproduce it here. Can you show paste the code just before the error occurs, then let me know what exact changes you make to trigger the error ?
Thanks !
> Java Model Exception occurs while typing
> ----------------------------------------
>
> Key: JBIDE-17947
> URL: https://issues.jboss.org/browse/JBIDE-17947
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Radoslav Rábara
> Assignee: Xavier Coulon
> Labels: respin-c
> Fix For: 4.2.0.Beta3
>
> Attachments: stack trace, video.ogv
>
>
> While editing JAX-RS resource class, the following exception shows up in Error log
> {code}
> Java Model Exception: Java Model Status [post() {key=LResource;.post()V} [in Resource [in [Working copy] Resource.java [in <default> [in src [in DynamicWebProject]]]]] does not exist]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17947) Java Model Exception occurs while typing
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17947?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-17947:
-------------------------------------
Assignee: Xavier Coulon
> Java Model Exception occurs while typing
> ----------------------------------------
>
> Key: JBIDE-17947
> URL: https://issues.jboss.org/browse/JBIDE-17947
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Radoslav Rábara
> Assignee: Xavier Coulon
> Labels: respin-c
> Fix For: 4.2.0.Beta3
>
> Attachments: stack trace, video.ogv
>
>
> While editing JAX-RS resource class, the following exception shows up in Error log
> {code}
> Java Model Exception: Java Model Status [post() {key=LResource;.post()V} [in Resource [in [Working copy] Resource.java [in <default> [in src [in DynamicWebProject]]]]] does not exist]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months