[JBoss JIRA] (JBIDE-19945) org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite failures
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19945?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19945:
----------------------------------
Fix Version/s: 4.3.0.Beta1
> 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
> Fix For: 4.3.0.Beta1
>
>
> {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
[JBoss JIRA] (JBIDE-19928) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Central]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19928?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-19928.
-------------------------------
Resolution: Done
Done for central
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Central]
> -----------------------------------------------------
>
> Key: JBIDE-19928
> URL: https://issues.jboss.org/browse/JBIDE-19928
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Central]: 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 Central 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-19928) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Central]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19928?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-19928:
-----------------------------------
Assignee: Fred Bricon
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Central]
> -----------------------------------------------------
>
> Key: JBIDE-19928
> URL: https://issues.jboss.org/browse/JBIDE-19928
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Central]: 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 Central 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] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ]
Fred Bricon resolved JBDS-3273.
-------------------------------
Resolution: Done
The bulk of the work is now done : quickstart list fetched from the dcp.jboss.org search engine every time Central is opened.
Marking as resolved. New tickets can be opened for the bugs we find.
> JBoss Central: Automatic upstream quickstart integration
> ---------------------------------------------------------
>
> Key: JBDS-3273
> URL: https://issues.jboss.org/browse/JBDS-3273
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 9.0.0.Beta1
>
>
> Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19943) checkup plugin give NPE in tests of webservices
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19943?page=com.atlassian.jira.plugi... ]
Denis Golovin reassigned JBIDE-19943:
-------------------------------------
Assignee: Daniel Azarov
> checkup plugin give NPE in tests of webservices
> -----------------------------------------------
>
> Key: JBIDE-19943
> URL: https://issues.jboss.org/browse/JBIDE-19943
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, webservices
> Reporter: Max Rydahl Andersen
> Assignee: Daniel Azarov
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> when running latest master tests I get this error in webservices:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.foundation.checkup.JVMProblemDetector.logging(JVMProblemDetector.java:321)
> at org.eclipse.core.internal.runtime.RuntimeLog.logToListeners(RuntimeLog.java:161)
> at org.eclipse.core.internal.runtime.PlatformLogWriter.logged(PlatformLogWriter.java:103)
> at org.eclipse.osgi.internal.log.ExtendedLogReaderServiceFactory.safeLogged(ExtendedLogReaderServiceFactory.java:88)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months