[JBoss JIRA] (JBIDE-17185) org.jboss.tools.cdi.core.test failures on Windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17185?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17185:
-----------------------------------
Attachment: org.jboss.tools.cdi.core.test.CDICoreAllTests-New.txt
> org.jboss.tools.cdi.core.test failures on Windows
> -------------------------------------------------
>
> Key: JBIDE-17185
> URL: https://issues.jboss.org/browse/JBIDE-17185
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.Beta1
> Environment: Windows
> Reporter: Daniel Azarov
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.Beta2
>
> Attachments: org.jboss.tools.cdi.core.test.CDICoreAllTests-New.txt, org.jboss.tools.cdi.core.test.CDICoreAllTests.txt
>
>
> Results :
> *Failed tests:*
> 1. testRemoveJarFromClasspath(org.jboss.tools.cdi.core.test.RemoveJarFromClasspathTest): cdi-simple.jar should be included into XModel.
> 2. testDependentProjects(org.jboss.tools.cdi.core.test.tck.validation.DependentProjectValidationTest): Marker matches the 'Injection point declares a primitive type boolean that cannot be proxied by the container resolves to a bean TestBean3.foo\(\) with a normal scope \[JSR-299 º5.4.1\]' pattern wasn't found. Here is the list of found markers in \CDITest3\src\cdi\test3\TestBean3.java : []
> 3. testAbstractApiType(org.jboss.tools.cdi.core.test.tck.BeanDefinitionTest): Location [start position=842, lengt=16] has not been found among the following locations: ([start position=885, length=16], [start position=860, length=16], )
> 4. testBeanTypes(org.jboss.tools.cdi.core.test.tck.BeanDefinitionTest): Location [start position=841, lengt=9] has not be
> en found among the following locations: ([start position=895, length=12], [start position=877, length=6], [start position=859, length=9], )
> 5. testBeanTypesNonEmpty(org.jboss.tools.cdi.core.test.tck.BeanDefinitionTest): Location [start position=914, lengt=10] has not been found among the following locations: ([start position=958, length=6], [start position=936, length=10], )
> 6. testNamedWithConstant(org.jboss.tools.cdi.core.test.tck.NameDefinitionTest): Wrong start position expected:<897> but was:<918>
> 7. testNonDefaultNamed(org.jboss.tools.cdi.core.test.tck.NameDefinitionTest): Wrong start position expected:<897> but was:<918>
> 8. testFieldInjectedFromProducerMethod(org.jboss.tools.cdi.core.test.tck.QualifierDefinitionTest): Location [start position=891, lengt=5] has not been found among the following locations: ([start position=914, length=5], )
> 9. testQualifiersDeclaredInJava(org.jboss.tools.cdi.core.test.tck.QualifierDefinitionTest): Location [start position=836, lengt=12] has not been found among the following locations: ([start position=856, length=12], )
> 10. testMultipleQualifiers(org.jboss.tools.cdi.core.test.tck.QualifierDefinitionTest): Location [start position=862, lengt=10] has not been found among the following locations: ([start position=882, length=10], [start position=894, length=24], [start position=920, length=19], )
> 11. testMultipleIncompatibleScopeStereotypesWithScopeSpecified (org.jboss.tools.cdi.core.test.tck.ScopeDefinitionTest): Location [start position=908, lengt=10] has not been found among the following locations: ([start position=930, length=10], )
> 12. testScopeDeclaredInJava(org.jboss.tools.cdi.core.test.tck.ScopeDefinitionTest): Location [start position=878, lengt=14] has not been found among the following locations: ([start position=898, length=14], )
> 13. testScopeSpecifiedAndStereotyped(org.jboss.tools.cdi.core.test.tck.ScopeDefinitionTest): Location [start position=899, lengt=14] has not been found among the following locations: ([start position=920, length=14], )
> 14. testScopeTypesAreExtensible(org.jboss.tools.cdi.core.test.tck.ScopeDefinitionTest): Location [start position=830, lengt=17] has not been found among the following locations: ([start position=848, length=17], )
> 15. testWebBeanScopeTypeOverridesStereotype(org.jboss.tools.cdi.core.test.tck.ScopeDefinitionTest): Location [start position=894, lengt=14] has not been found among the following locations: ([start position=915, length=14], )
> 16. testMultipleStereotypesAllowed(org.jboss.tools.cdi.core.test.tck.StereotypeDefinitionTest): Location [start position=877, lengt=5] has not been found among the following locations: ([start position=897, length=5], )
> 17. testStereotypeWithScopeType(org.jboss.tools.cdi.core.test.tck.StereotypeDefinitionTest): Location [start position=835, lengt=17] has not been found among the following locations: ([start position=853, length=17], )
> 18. testBindingTypesAppliedToProducerMethodParameters (org.jboss.tools.cdi.core.test.tck.ProducerMethodDefinitionTest): Location [start position=1287, lengt=29] has not been found among the following locations: ([start position=1319, length=29], [start position=1361, length=19], )
> 19. testInitializerMethodHasParameterAnnotatedDisposes (org.jboss.tools.cdi.core.test.tck.validation.DefenitionErrorsValidationTest): Marker matches the 'Disposer method cannot be annotated @Inject \[JSR-299 º3.3.6\]' pattern wasn't found for line - 25, start - 979, end - 986. Found markers for given patern: [line number - 25, start - 1003, end - 1010; line number - 26, start - 1048, end - 1057]
> 20. testRestrictedType(org.jboss.tools.cdi.core.test.tck.validation.IncrementalValidationTest): Marker matches the 'Bean specifies a type restriction which does not correspond to a type in the unrestricted set of bean types of a bean \[JSR-299 º2.2.2\]' pattern was found
> 21. testInjectionsWithInterface(org.jboss.tools.cdi.core.test.tck.validation.IncrementalValidationTest): Marker matches the 'No bean is eligible for injection to the injection point \[JSR-299 º5.2.1\]' pattern wasn't found. Here is the list of found markers in \tck\JavaSource\org\jboss\jsr299\tck\tests\jbt\validation\inject\incremental\ExtensionManager.java :[]
> 22. testAlternativesInBeansXml(org.jboss.tools.cdi.core.test.tck.validation.IncrementalValidationTest): Marker matches the 'No bean is eligible for injection to the injection point \[JSR-299 º5.2.1\]' pattern wasn't found. Here is the list of found markers in \tck\JavaSource\org\jboss\jsr299\tck\tests\jbt\validation\beansxml\incremental\Test3.java : []
> 23. testInjectionPointRevalidation(org.jboss.tools.cdi.core.test.tck.validation.IncrementalValidationTest): Marker matches the 'Multiple beans are eligible for injection to the injection point \[JSR-299 º5.2.1\]' pattern was found
> 24. testInjectionPointResolvedToProducerRevalidation (org.jboss.tools.cdi.core.test.tck.validation.IncrementalValidationTest): Marker matches the 'Multiple beans are eligible for injection to the injection point \[JSR-299 º5.2.1\]' pattern was found
> 25. testNamedBeanClassRename(org.jboss.tools.cdi.core.test.tck.NamedBeanRefactoringTest): There is unexpected change in resource - Gamme.java expected:<[abcde]> but was:<[ed
> 26. testAbstractApiType(org.jboss.tools.cdi.core.test.tck11.BeanDefinitionCDI11Test): Location [start position=842, lengt=16] has not been found among the following locations: ([start position=885, length=16], [start position=860, length=16], )
> 27. testBeanTypes(org.jboss.tools.cdi.core.test.tck11.BeanDefinitionCDI11Test): Location [start position=841, lengt=9] has not been found among the following locations: ([start position=859, length=9], [start position=877, length=6], [start position=895, length=12], )
> 28. testBeanTypesNonEmpty(org.jboss.tools.cdi.core.test.tck11.BeanDefinitionCDI11Test): Location [start position=914, lengt=10] has not been found among the following locations: ([start position=958, length=6], [start position=936, length=10], )
> 29. testNamedWithConstant(org.jboss.tools.cdi.core.test.tck11.NameDefinitionCDI11Test): Wrong start position expected:<897> but was:<918>
> 30. testNonDefaultNamed(org.jboss.tools.cdi.core.test.tck11.NameDefinitionCDI11Test): Wrong start position expected:<897> but was:<918>
> 31. testFieldInjectedFromProducerMethod(org.jboss.tools.cdi.core.test.tck11.QualifierDefinitionCDI11Test): Location [start position=891, lengt=5] has not been found among the following locations: ([start position=914, length=5], )
> 32. testQualifiersDeclaredInJava(org.jboss.tools.cdi.core.test.tck11.QualifierDefinitionCDI11Test): Location [start position=836, lengt=12] has not been found among the following locations: ([start position=856, length=12], )
> 33. testMultipleQualifiers(org.jboss.tools.cdi.core.test.tck11.QualifierDefinitionCDI11Test): Location [start position=862, lengt=10] has not been found among the following locations: ([start position=882, length=10], [start position=894, length=24], [start position=920, length=19], )
> 34. testMultipleIncompatibleScopeStereotypesWithScopeSpecified (org.jboss.tools.cdi.core.test.tck11.ScopeDefinitionCDI11Test): Location [start position=908, lengt=10] has not been found among the following locations: ([start position=930, length=10], )
> 35. testScopeDeclaredInJava(org.jboss.tools.cdi.core.test.tck11.ScopeDefinitionCDI11Test): Location [start position=878, lengt=14] has not been found among the following locations: ([start position=898, length=14], )
> 36. testScopeSpecifiedAndStereotyped(org.jboss.tools.cdi.core.test.tck11.ScopeDefinitionCDI11Test): Location [start position=899, lengt=14] has not been found among the following locations: ([start position=920, length=14], )
> 37. testScopeTypesAreExtensible(org.jboss.tools.cdi.core.test.tck11.ScopeDefinitionCDI11Test): Location [start position=830, lengt=17] has not been found among the following locations: ([start position=848, length=17], )
> 38. testWebBeanScopeTypeOverridesStereotype(org.jboss.tools.cdi.core.test.tck11.ScopeDefinitionCDI11Test): Location [start position=894, lengt=14] has not been found among the following locations: ([start position=915, length=14], )
> 39. testMultipleStereotypesAllowed(org.jboss.tools.cdi.core.test.tck11.StereotypeDefinitionCDI11Test): Location [start position=877, lengt=5] has not been found among the following locations: ([start position=897, length=5], )
> 40. testStereotypeWithScopeType(org.jboss.tools.cdi.core.test.tck11.StereotypeDefinitionCDI11Test): Location [start position=835, lengt=17] has not been found among the following locations: ([start position=853, length=17], )
> 41. testBindingTypesAppliedToProducerMethodParameters (org.jboss.tools.cdi.core.test.tck11.ProducerMethodDefinitionCDI11Test): Location [start position=1287, lengt=29] has not been found among the following locations: ([start position=1319, length=29], [start position=1361, length=19], )
> 42. testInitializerMethodHasParameterAnnotatedDisposes (org.jboss.tools.cdi.core.test.tck11.validation.DefenitionErrorsValidationCDI11Test): Marker matches the 'Disposer method cannot be annotated @Inject \[JSR-299 º3.3.6\]' pattern wasn't found for line - 25, start - 979, end - 986. Found markers for given patern: [line number - 25, start - 1003, end - 1010; line number - 26, start - 1048, end - 1057]
> 43. testRestrictedType(org.jboss.tools.cdi.core.test.tck11.validation.IncrementalValidationCDI11Test): Marker matches the 'Bean specifies a type restriction which does not correspond to a type in the unrestricted set of bean types of a bean \[JSR-299 º2.2.2\]' pattern was found
> 44. testInjectionsWithInterface(org.jboss.tools.cdi.core.test.tck11.validation.IncrementalValidationCDI11Test): Marker matches the 'No bean is eligible for injection to the injection point \[JSR-299 º5.2.1\]' pattern wasn't found. Here is the list of found markers in \tck1.1\JavaSource\org\jboss\jsr299\tck\tests\jbt\validation\inject\incremental\ExtensionManager.java : []
> 45. testAlternativesInBeansXml(org.jboss.tools.cdi.core.test.tck11.validation.IncrementalValidationCDI11Test): Marker matches the 'No bean is eligible for injection to the injection point \[JSR-299 º5.2.1\]' pattern wasn't found. Here is the list of found markers in \tck1.1\JavaSource\org\jboss\jsr299\tck\tests\jbt\validation\beansxml\incremental\Test3.java : []
> 46. testInjectionPointRevalidation(org.jboss.tools.cdi.core.test.tck11.validation.IncrementalValidationCDI11Test): Marker matches the 'Multiple beans are eligible for injection to the injection point \[JSR-299 º5.2.1\]' pattern was found
> 47. testInjectionPointResolvedToProducerRevalidation (org.jboss.tools.cdi.core.test.tck11.validation.IncrementalValidationCDI11Test): Marker matches the 'Multiple beans are eligible for injection to the injection point \[JSR-299 º5.2.1\]' pattern was found
> 48. testNamedBeanClassRename(org.jboss.tools.cdi.core.test.tck11.NamedBeanRefactoringCDI11Test): There is unexpected change in resource - Gamme.java expected:<[abcde]> but was:<[ed
> *Tests in error:*
> 1. testParameterizedTypeWithWildcard(org.jboss.tools.cdi.core.test.tck.validation.DefenitionErrorsValidationTest): Resource '/tck/JavaSource/org/jboss/jsr299/tck/tests/implementation/producer/field/definition/broken/parameterizedReturnTypeWithWildcard/SpiderProducerWildCardType_Broken.java' does not exist.
> 2. testParameterizedTypeWithWildcard(org.jboss.tools.cdi.core.test.tck.validation.AYTDefenitionErrorsValidationTest): Resource '/tck/JavaSource/org/jboss/jsr299/tck/tests/implementation/producer/field/definition/broken/parameterizedReturnTyp
> eWithWildcard/SpiderProducerWildCardType_Broken.java' does not exist.
> 3. testParameterizedTypeWithWildcard (org.jboss.tools.cdi.core.test.tck11.validation.DefenitionErrorsValidationCDI11Test):
> Resource '/tck1.1/JavaSource/org/jboss/jsr299/tck/tests/implementation/producer/field/definition/broken/parameterizedReturnTypeWithWildcard/SpiderProducerWildCardType_Broken.java' does not exist.
> 4. testParameterizedTypeWithWildcard (org.jboss.tools.cdi.core.test.tck11.validation.AYTDefenitionErrorsValidationCDI11Test): Resource '/tck1.1/JavaSource/org/jboss/jsr299/tck/tests/implementation/producer/field/definition/broken/parameterize
> dReturnTypeWithWildcard/SpiderProducerWildCardType_Broken.java' does not exist.
> Tests run: 1283, Failures: 48, Errors: 4, Skipped: 0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBIDE-17193) org.jboss.tools.cdi.seam.config.core.test failures on Windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17193?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-17193.
------------------------------------
Resolution: Done
Fixed by the PR for JBIDE-17195
> org.jboss.tools.cdi.seam.config.core.test failures on Windows
> -------------------------------------------------------------
>
> Key: JBIDE-17193
> URL: https://issues.jboss.org/browse/JBIDE-17193
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions
> Affects Versions: 4.2.0.Beta1
> Environment: Windows
> Reporter: Daniel Azarov
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.2.0.Beta2
>
> Attachments: org.jboss.tools.cdi.seam.config.core.test.CDISeamConfigCoreAllTests.txt, org.jboss.tools.cdi.seam.config.core.test.v30.CDISeamConfigCoreAllTests30.txt
>
>
> Tests run: 51, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 6.204 sec <<< FAILURE!
> Results :
> Failed tests: testAddClassToResolveNode(org.jboss.tools.cdi.seam.config.core.test.v30.SeamConfigValidationTest): Marker matches the 'Cannot resolve type org.jboss.beans.validation.test.MyBean2.' pattern wasn't found. Here is the list of found markers in \CDIConfigValidationTest30\src\META-INF\beans.xml : [ testBeanResolution(org.jboss.tools.cdi.seam.config.core.test.v30.SeamConfigValidationTest): Marker matches the 'Cannot
> resolve type org.jboss.beans.validation.test.MyBean2.' pattern wasn't found. Here is the list of found markers in CDIConfigValidationTest30\src\META-INF\beans.xml : [
> testAddClassToResolveNode(org.jboss.tools.cdi.seam.config.core.test.SeamConfigValidationTest): Marker matches the 'Cannot resolve type org.jboss.beans.validation.test.MyBean2.' pattern wasn't found. Here is the list of found markers in \CDIConfigValidationTest\src\META-INF\beans.xml : [
> testBeanResolution(org.jboss.tools.cdi.seam.config.core.test.SeamConfigValidationTest): Marker matches the 'Cannot resolve type org.jboss.beans.validation.test.MyBean2.' pattern wasn't found. Here is the list of found markers in \CDIConfigValidationTest\src\META-INF\beans.xml : [
> testAddClassToResolveNode(org.jboss.tools.cdi.seam.config.core.test.v30.SeamConfigValidationTest): Marker matches the 'Cannot resolve type org.jboss.beans.validation.test.MyBean2.' pattern wasn't found. Here is the list of found markers in \CDIConfigValidationTest30\src\META-INF\beans.xml : [
> testBeanResolution(org.jboss.tools.cdi.seam.config.core.test.v30.SeamConfigValidationTest): Marker matches the 'Cannot resolve type org.jboss.beans.validation.test.MyBean2.' pattern wasn't found. Here is the list of found markers in \CDIConfigValidationTest30\src\META-INF\beans.xml : [
> Tests run: 156, Failures: 6, Errors: 0, Skipped: 0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBIDE-17065) Cordova Download window: 'platform' table label changes colour on mouse over
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17065?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-17065:
--------------------------------------
Hi Michelle,
I can not really reproduce this. Are you on windows?
> Cordova Download window: 'platform' table label changes colour on mouse over
> ----------------------------------------------------------------------------
>
> Key: JBIDE-17065
> URL: https://issues.jboss.org/browse/JBIDE-17065
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Attachments: HMT_CordovaDownload.png
>
>
> The Download Hybrid Mobile Engine window has a table listing platforms for which to download specific Cordova versions. The table has a row header 'platform'. This label is greyed out and when I move the mouse over it it become black but this label appears to have no functionality so shouldn't be changing colour as far as I can see.
> !HMT_CordovaDownload.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBIDE-16883) Broken UI logic in Hybrid Mobile/ Engine properties
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16883?page=com.atlassian.jira.plugi... ]
Gorkem Ercan resolved JBIDE-16883.
----------------------------------
Assignee: Gorkem Ercan
Resolution: Done
> Broken UI logic in Hybrid Mobile/ Engine properties
> ---------------------------------------------------
>
> Key: JBIDE-16883
> URL: https://issues.jboss.org/browse/JBIDE-16883
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78, Linux
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.2.0.Beta2
>
> Attachments: enginesearch.png
>
>
> Case 0:
> 1. Open Window > Preferences > Hybrid Mobile > Engines with no engines defined
> 2. Resize Preferences window
> ERROR: Engine table is not resized
> Case 1:
> 1. Open Window > Preferences > Hybrid Mobile > Engines with no engines defined
> 2. Click on another Preferences tree item
> ERROR: It's not possible to select another preferences. Error dialog is displayed saying: "The currently displayed page contains invalid values"
> Case 2:
> 1. Use this preferences dialog to download Hybrid Mobile engine
> ERROR: Displayed Progress Bar has only two values 0% and 100% there is no progress change during downloading
> ERROR: OK button within Download Hybrid Mobile Engine dialog should be enabled only when version and at least one platform is selected
> ERROR: When first engine is downloaded it should be marked as default automatically
> ERROR: While downloading OK button, Version Combo and Platform Table are is still enabled
> Case 3:
> 1. Remove all downloaded engines by clicking on button Remove
> ERROR: Engines are removed immediately after Remove button is clicked. They should be really removed when button OK is pushed
> ERROR: Once there is no engine in dialog error from Case 1 happens
> Case 4:
> 1. Remove all downloaded engines
> 2. Reopen preferences dialog
> 3. Download engine
> 4. Check downloaded engine as default
> ERROR: Button OK is still disabled.
> 5. Uncheck default button
> 6. Check default button
> 7. OK button is enabled and it's possible to click on it
> Case 5:
> 1. Download at least 1 engine
> 2. Search for engine on local file system more times using the same directory
> ERROR: Platform in table is "Android Android ..."
> 3. Click on i image in third column
> ERROR: It shows more than one line with engine location and shows incorrect location for files found on local file system not downloaded from repo
> !enginesearch.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBIDE-16883) Broken UI logic in Hybrid Mobile/ Engine properties
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16883?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-16883:
--------------------------------------
This is a lot of different issues bundled into one. It would be better if we had separate issues for them.
Case 1: I do not think this is actually an issue. This is the way preference dialogs work if a page is invalid, in this case there are no engines selected the message comes from the eclipse platform itself. You can try to unselect your default JRE and move to another eclipse preference node to see the same behaviour.
Case 2: Some part of this is addressed in JBIDE-17062. OK button is disabled until all selections are done and the versions and platforms are disabled when ok is selected.
There is not much we can do for the download progress because the download source does not report the progress but otherwise all the plumbing is in place.
Fixed the default selection for these when there is only a single engine.
Case 3: Remove button is meant to remove immediately, again this is very similar to JRE dialog.
Case 4: I can not reproduce this case after changes due to case 2
Case 5: Can you open a separate one for this case as it is more than a UI issue.
> Broken UI logic in Hybrid Mobile/ Engine properties
> ---------------------------------------------------
>
> Key: JBIDE-16883
> URL: https://issues.jboss.org/browse/JBIDE-16883
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78, Linux
> Reporter: Vlado Pakan
> Priority: Critical
> Fix For: 4.2.0.Beta2
>
> Attachments: enginesearch.png
>
>
> Case 0:
> 1. Open Window > Preferences > Hybrid Mobile > Engines with no engines defined
> 2. Resize Preferences window
> ERROR: Engine table is not resized
> Case 1:
> 1. Open Window > Preferences > Hybrid Mobile > Engines with no engines defined
> 2. Click on another Preferences tree item
> ERROR: It's not possible to select another preferences. Error dialog is displayed saying: "The currently displayed page contains invalid values"
> Case 2:
> 1. Use this preferences dialog to download Hybrid Mobile engine
> ERROR: Displayed Progress Bar has only two values 0% and 100% there is no progress change during downloading
> ERROR: OK button within Download Hybrid Mobile Engine dialog should be enabled only when version and at least one platform is selected
> ERROR: When first engine is downloaded it should be marked as default automatically
> ERROR: While downloading OK button, Version Combo and Platform Table are is still enabled
> Case 3:
> 1. Remove all downloaded engines by clicking on button Remove
> ERROR: Engines are removed immediately after Remove button is clicked. They should be really removed when button OK is pushed
> ERROR: Once there is no engine in dialog error from Case 1 happens
> Case 4:
> 1. Remove all downloaded engines
> 2. Reopen preferences dialog
> 3. Download engine
> 4. Check downloaded engine as default
> ERROR: Button OK is still disabled.
> 5. Uncheck default button
> 6. Check default button
> 7. OK button is enabled and it's possible to click on it
> Case 5:
> 1. Download at least 1 engine
> 2. Search for engine on local file system more times using the same directory
> ERROR: Platform in table is "Android Android ..."
> 3. Click on i image in third column
> ERROR: It shows more than one line with engine location and shows incorrect location for files found on local file system not downloaded from repo
> !enginesearch.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JBIDE-17202) Importing/building WildFly 8.0.Final into JBTools 4.2.0.Beta1 results in GC faillure with Java 1.7.0
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17202?page=com.atlassian.jira.plugi... ]
Len DiMaggio updated JBIDE-17202:
---------------------------------
Attachment: jbosstools-diagnostics-20140428140420.zip
> Importing/building WildFly 8.0.Final into JBTools 4.2.0.Beta1 results in GC faillure with Java 1.7.0
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17202
> URL: https://issues.jboss.org/browse/JBIDE-17202
> Project: Tools (JBoss Tools)
> Issue Type: Quality Risk
> Components: build
> Affects Versions: 4.2.0.Beta1
> Environment: Linux 2.6.32-358.23.2.el6.x86_64 #1 SMP Sat Sep 14 05:32:37 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux
> java -version
> java version "1.7.0_25"
> OpenJDK Runtime Environment (rhel-2.3.10.4.el6_4-x86_64)
> OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
> Reporter: Len DiMaggio
> Attachments: jbosstools-diagnostics-20140428140420.zip, log, Screenshot-1.png, Screenshot-2.png, Screenshot.png
>
>
> See attached logs and screenshots - building WildFly causes a GC failure
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months