[JBoss JIRA] (TOOLSDOC-650) Add Android SDK installation info into the Community docs
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-650?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-650:
-------------------------------
Summary: Add Android SDK installation info into the Community docs (was: Add the info in the Community docs)
> Add Android SDK installation info into the Community docs
> ---------------------------------------------------------
>
> Key: TOOLSDOC-650
> URL: https://issues.jboss.org/browse/TOOLSDOC-650
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Components: General documentation issues
> Reporter: Supriya Bharadwaj
> Assignee: Misha Ali
> Priority: Minor
> Fix For: 4.2.3.Final
>
> Attachments: fh_android_preferences.png, fh_import_install_android_sdk.adoc, first_hybrid_app_android_preferences.png, first_hybrid_app_install_android_sdk.adoc
>
>
> Please add the info in the community versions of the documents
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (TOOLSDOC-650) Add the info in the Community docs
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-650?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-650:
------------------------------------
[~supriya.bharadwaj], it occurs to me that in the future it may reduce the margin for error by having you locate the appropriate adoc file in the jboss tools docs git repo and copy it locally, then make the changes/insertions required, test it locally by viewing it and then adding that file as an attachment. The benefits of this approach are:
* You have greater control over the placement and formatting of the changes/insertions
* You test it as you write the content, so this means I can just paste the exact changes you require in and let you know they are available.
This occurs to me because while you got the image::<name of image> part correct this time, the formatting of the image is not correct:
Select the Android SDK Location
image::first_hybrid_app_android_preferences.png[Select the Android SDK Location]
. Click `Apply` and then click `OK`.
This would not render corrected upon testing. This should be:
.Select the Android SDK Location
image::first_hybrid_app_android_preferences.png[Select the Android SDK Location]
What do you think about the new approach?
> Add the info in the Community docs
> ----------------------------------
>
> Key: TOOLSDOC-650
> URL: https://issues.jboss.org/browse/TOOLSDOC-650
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Components: General documentation issues
> Reporter: Supriya Bharadwaj
> Assignee: Misha Ali
> Priority: Minor
> Fix For: 4.2.3.Final
>
> Attachments: fh_android_preferences.png, fh_import_install_android_sdk.adoc, first_hybrid_app_android_preferences.png, first_hybrid_app_install_android_sdk.adoc
>
>
> Please add the info in the community versions of the documents
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (TOOLSDOC-650) Add the info in the Community docs
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-650?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-650:
------------------------------------
Hi [~supriya.bharadwaj]. Regarding the second comment (none of these should be RH only, btw), yes, the images are defined in this way. Good initiative looking up the exact format in the github comments yourself rather than asking!
> Add the info in the Community docs
> ----------------------------------
>
> Key: TOOLSDOC-650
> URL: https://issues.jboss.org/browse/TOOLSDOC-650
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Components: General documentation issues
> Reporter: Supriya Bharadwaj
> Assignee: Misha Ali
> Priority: Minor
> Fix For: 4.2.3.Final
>
> Attachments: fh_android_preferences.png, fh_import_install_android_sdk.adoc, first_hybrid_app_android_preferences.png, first_hybrid_app_install_android_sdk.adoc
>
>
> Please add the info in the community versions of the documents
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19912) For JBIDE 4.3.0.Beta1: Code Freeze + Branch
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19912?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-19912.
------------------------------
Assignee: Nick Boldt
Resolution: Done
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch
> -------------------------------------------
>
> Key: JBIDE-19912
> URL: https://issues.jboss.org/browse/JBIDE-19912
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Beta1x
> git push origin jbosstools-4.3.0.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and
> * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3451
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19913) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Aerogear]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19913?page=com.atlassian.jira.plugi... ]
Gorkem Ercan reassigned JBIDE-19913:
------------------------------------
Assignee: Gorkem Ercan
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Aerogear]
> ------------------------------------------------------
>
> Key: JBIDE-19913
> URL: https://issues.jboss.org/browse/JBIDE-19913
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid, cordovasim
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Aerogear]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Beta1x
> git push origin jbosstools-4.3.0.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and
> * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19913) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Aerogear]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19913?page=com.atlassian.jira.plugi... ]
Gorkem Ercan closed JBIDE-19913.
--------------------------------
Resolution: Done
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Aerogear]
> ------------------------------------------------------
>
> Key: JBIDE-19913
> URL: https://issues.jboss.org/browse/JBIDE-19913
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid, cordovasim
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Aerogear]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Beta1x
> git push origin jbosstools-4.3.0.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and
> * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19631) Switch Tern.java dependency version range to the only version after code freeze
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19631?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19631:
---------------------------------------
Victor suggested to switch to latest snapshot build 0.10.0.201506020610
but I have test errors with suggested tern.
{code}Running org.jboss.tools.jst.jsdt.test.JstJsdtAllTests
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 8.9 sec <<< FAILURE! - in org.jboss.tools.jst.jsdt.test.JstJsdtAllTests
testJstJsdtTernCAOnBrowser(org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest) Time elapsed: 3.725 sec <<< FAILURE!
junit.framework.AssertionFailedError: Content Assistant returned no proposals
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.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:79)
at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnBrowser(JstJsdtTernCATest.java:65)
testJstJsdtTernCAOnEcma5(org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest) Time elapsed: 1.878 sec <<< FAILURE!
junit.framework.AssertionFailedError: Content Assistant returned no proposals
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.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:79)
at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma5(JstJsdtTernCATest.java:61)
Results :
Failed tests:
JstJsdtTernCATest.testJstJsdtTernCAOnBrowser:65->doJstJsdtTernCATest:79 Content Assistant returned no proposals
JstJsdtTernCATest.testJstJsdtTernCAOnEcma5:61->doJstJsdtTernCATest:79 Content Assistant returned no proposals
Tests run: 2, Failures: 2, Errors: 0, Skipped: 0{code}
> Switch Tern.java dependency version range to the only version after code freeze
> -------------------------------------------------------------------------------
>
> Key: JBIDE-19631
> URL: https://issues.jboss.org/browse/JBIDE-19631
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied.
> For every development/stable release the open range should be replaced to specific version.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19945) org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite failures
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-19945:
-------------------------------------
Summary: org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite failures
Key: JBIDE-19945
URL: https://issues.jboss.org/browse/JBIDE-19945
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Reporter: Daniel Azarov
{code}
-------------------------------------------------------------------------------
Test set: org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
-------------------------------------------------------------------------------
Tests run: 7, Failures: 4, Errors: 1, Skipped: 0, Time elapsed: 22.278 sec <<< FAILURE! - in org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest) Time elapsed: 0.002 sec <<< FAILURE!
junit.framework.AssertionFailedError: The JRE5 location is not right
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.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69)
at org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.setUp(JBossWSTopDownCommandTest.java:59)
testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest) Time elapsed: 0.508 sec <<< ERROR!
java.lang.NullPointerException: null
at org.eclipse.jdt.launching.AbstractVMInstall.setName(AbstractVMInstall.java:120)
at org.jboss.tools.as.test.core.internal.utils.JREUtils.createJRE(JREUtils.java:104)
at org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.setUp(JBossWSJavaFirstCommandTest.java:64)
testInitialClientCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 0 sec <<< FAILURE!
junit.framework.AssertionFailedError: The JRE5 location is not right
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.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69)
at org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.setUp(JBossWSClientCommandTest.java:48)
testClientCodeGenerationCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 0.001 sec <<< FAILURE!
junit.framework.AssertionFailedError: The JRE5 location is not right
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.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69)
at org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.setUp(JBossWSClientCommandTest.java:48)
testRemoveClientJarsCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 0 sec <<< FAILURE!
junit.framework.AssertionFailedError: The JRE5 location is not right
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.ws.creation.core.test.command.AbstractJBossWSGenerationTest.setUp(AbstractJBossWSGenerationTest.java:69)
at org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.setUp(JBossWSClientCommandTest.java:48)
testMergeWebXMLCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest) Time elapsed: 16.904 sec
testJBIDE6175(org.jboss.tools.ws.creation.core.test.command.JBossWSClientSampleCreationCommandTest) Time elapsed: 4.789 sec
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months