[JBoss JIRA] (JBIDE-17184) org.jboss.tools.jsf.ui.test failure on Windows
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17184?page=com.atlassian.jira.plugi... ]
Daniel Azarov commented on JBIDE-17184:
---------------------------------------
I did. Tests pass on my Windows 8.1
> org.jboss.tools.jsf.ui.test failure on Windows
> ----------------------------------------------
>
> Key: JBIDE-17184
> URL: https://issues.jboss.org/browse/JBIDE-17184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.2.0.Beta1
> Reporter: Daniel Azarov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Beta2
>
> Attachments: Linux17184.png, org.jboss.tools.jsf.ui.test.JsfUiAllTests.txt, Windows17184.png, Windows17184.png
>
>
> Tests run: 104, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 738.449 sec <<< FAILURE!
> Results :
> Failed tests: testMessagesInLocalizedBundles(org.jboss.tools.jsf.jsp.ca.test.CAJsfMessagesProposalsTest): The proposal to apply not found.
> Tests run: 104, Failures: 1, Errors: 0, Skipped: 0
--
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 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.
See also: http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platform.do...
was: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)
> * {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.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17390) jsf.ui test failure
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17390?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-17390.
-------------------------------
Tests are not failing because they are not run.
Can't say it's proper fix.
Consider to mark them ignored in that case it will be harder to forget to enable them once it will be needed. They will be included in Test results report.
> jsf.ui test failure
> -------------------
>
> Key: JBIDE-17390
> URL: https://issues.jboss.org/browse/JBIDE-17390
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.2.0.Beta2
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Beta2
>
>
> {code}
> testJsfImplementationsPreferencesPage(org.jboss.tools.jsf.ui.test.JsfUiPreferencesPagesTest) Time elapsed: 0.25 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Selected page is not an instance of PreferencePage
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.tests.PreferencePageTest.doDefaultTest(PreferencePageTest.java:51)
> at org.jboss.tools.jsf.ui.test.JsfUiPreferencesPagesTest.testJsfImplementationsPreferencesPage(JsfUiPreferencesPagesTest.java:35)
> testJsfCapabilitiesPreferencesPage(org.jboss.tools.jsf.ui.test.JsfUiPreferencesPagesTest) Time elapsed: 0.152 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Selected page is not an instance of PreferencePage
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.tests.PreferencePageTest.doDefaultTest(PreferencePageTest.java:51)
> at org.jboss.tools.jsf.ui.test.JsfUiPreferencesPagesTest.testJsfCapabilitiesPreferencesPage(JsfUiPreferencesPagesTest.java:27)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17182) org.jboss.tools.jsf.test tests failure on Windows
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17182?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-17182:
-------------------------------------
Please could you verify this Jira?
> org.jboss.tools.jsf.test tests failure on Windows
> -------------------------------------------------
>
> Key: JBIDE-17182
> URL: https://issues.jboss.org/browse/JBIDE-17182
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.2.0.Beta1
> Environment: Windows
> Reporter: Daniel Azarov
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.Beta2
>
> Attachments: org.jboss.tools.jsf.test.JsfAllTests.txt
>
>
> Tests run: 84, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 111.373 sec <<< FAILURE!
> Results :
> Failed tests: testPerformanceOfCalculatingLineNumbers(org.jboss.tools.jsf.test.validation.ELValidatorTest): Wrong line number
> testELVariableRename(org.jboss.tools.jsf.test.refactoring.ELVariableRefactoringTest): There is unexpected change in resource - el.jsp expected:<[cust]> but was:<[#{cu]>
> Tests in error:
> testWebContentValidation(org.jboss.tools.jsf.test.validation.XHTMLValidatorTest): / by zero
> Tests run: 109, Failures: 2, Errors: 1, Skipped: 0
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17184) org.jboss.tools.jsf.ui.test failure on Windows
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17184?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-17184:
-------------------------------------
Please could you verify this Jira?
> org.jboss.tools.jsf.ui.test failure on Windows
> ----------------------------------------------
>
> Key: JBIDE-17184
> URL: https://issues.jboss.org/browse/JBIDE-17184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.2.0.Beta1
> Reporter: Daniel Azarov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Beta2
>
> Attachments: Linux17184.png, org.jboss.tools.jsf.ui.test.JsfUiAllTests.txt, Windows17184.png, Windows17184.png
>
>
> Tests run: 104, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 738.449 sec <<< FAILURE!
> Results :
> Failed tests: testMessagesInLocalizedBundles(org.jboss.tools.jsf.jsp.ca.test.CAJsfMessagesProposalsTest): The proposal to apply not found.
> Tests run: 104, Failures: 1, Errors: 0, Skipped: 0
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17183) org.jboss.tools.jsf.text.ext.test failure on Windows
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17183?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-17183:
-------------------------------------
Please could you verify this Jira?
> org.jboss.tools.jsf.text.ext.test failure on Windows
> ----------------------------------------------------
>
> Key: JBIDE-17183
> URL: https://issues.jboss.org/browse/JBIDE-17183
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.2.0.Beta1
> Environment: Windows
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Beta2
>
> Attachments: org.jboss.tools.jsf.text.ext.test.JsfTextExtAllTests.txt
>
>
> Tests run: 54, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 106.758 sec <<< FAILURE!
> Results :
> Failed tests: testCCAttrsHyperlink1(org.jboss.tools.jsf.text.ext.test.JSF2CCAttrsOpenOnTest): Wrong detection for regi
> on - 658 - 665 line - 17 position - 14 offset - 658 (line - 16 position - 14)
> testCCAttrsHyperlink2(org.jboss.tools.jsf.text.ext.test.JSF2CCAttrsOpenOnTest): Wrong detection for region - 610 - 617
> line - 17 position - 14 offset - 610 (line - 16 position - 14)
> testCCAttrsHyperlink1(org.jboss.tools.jsf.text.ext.test.JSF22CCAttrsOpenOnTest): Wrong detection for region - 660 - 667 line - 17 position - 14 offset - 660 (line - 16 position - 14)
> testCCAttrsHyperlink2(org.jboss.tools.jsf.text.ext.test.JSF22CCAttrsOpenOnTest): Wrong detection for region - 612 - 619 line - 17 position - 14 offset - 612 (line - 16 position - 14)
> Tests run: 54, Failures: 4, Errors: 0, Skipped: 0
--
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:
-----------------------------
Description:
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
was:
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
> 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)
> * {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.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17217) [javascript] Add an adapter for AngularJS-eclipse
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17217?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-17217.
-------------------------------
Verified with JBDS 8.0.0.Beta2-v20140525-2146-B104
> [javascript] Add an adapter for AngularJS-eclipse
> -------------------------------------------------
>
> Key: JBIDE-17217
> URL: https://issues.jboss.org/browse/JBIDE-17217
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core, jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta1
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.Beta2
>
>
> It's abe to make AngularJS-eclipse to use a specified nature instead of the its own one by using an extension point provided by AngularJS-eclipse.
> Need to add such a point to make it work for plain JavaScript projects.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-13808) Test failures and timeouts in JSF tests
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13808?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-13808.
-------------------------------
> Test failures and timeouts in JSF tests
> ---------------------------------------
>
> Key: JBIDE-13808
> URL: https://issues.jboss.org/browse/JBIDE-13808
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf, visual-page-editor-core
> Affects Versions: 4.0.1.Final
> Reporter: Nick Boldt
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Fix For: 4.2.0.Beta2
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--javaee/146/console}
> [INFO] org.jboss.tools.jsf.text.ext.test ................. FAILURE [1:20.290s]
> [INFO] org.jboss.tools.jsf.vpe.facelets.test ............. FAILURE [1:00:28.012s]
> [INFO] org.jboss.tools.jsf.vpe.jbpm.test ................. FAILURE [1:00:24.806s]
> [INFO] org.jboss.tools.jsf.vpe.jstl.test ................. FAILURE [1:00:25.978s]
> [INFO] org.jboss.tools.jsf.vpe.seam.test ................. FAILURE [1:00:28.143s]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.text.ext.test: An unexpected error occured (return code 134). See log for details. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.facelets.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.jbpm.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.jstl.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.seam.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months