[JBoss JIRA] (JBIDE-16207) For JBIDE 4.1.1.Final: Prepare for Final/GA release [Webservices]
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16207?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-16207.
------------------------------------
Resolution: Done
re-closing
> For JBIDE 4.1.1.Final: Prepare for Final/GA release [Webservices]
> -----------------------------------------------------------------
>
> Key: JBIDE-16207
> URL: https://issues.jboss.org/browse/JBIDE-16207
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Final
>
>
> For JBIDE 4.1.1.Final [Webservices]: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> 2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.2.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.30.6.Final
> mvn clean verify -Dtpc.version=4.31.1.Final
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16203) For JBIDE 4.1.1.Final: Prepare for Final/GA release [OpenShift]
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16203?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-16203 at 12/6/13 1:45 PM:
-------------------------------------------------------------------
4.1.1.x
{code}
mvn clean verify -Dtpc.version=4.30.6.Final -Dtycho.localArtifacts=ignore
{code}
{code}
[INFO] --- repository-utils:0.16.0.CR2:generate-repository-facade (generate-facade) @ openshift.site ---
[WARNING] No org.jboss.tools.central.discovery plugin in repo. Skip generation of 'jbosstools-directory.xml'
[INFO] Building zip: /home/adietish/jboss-workspaces/jbosstools-github/jbosstools-openshift/site/target/openshift.site-2.5.1-SNAPSHOT.zip
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] openshift.all ..................................... SUCCESS [0.566s]
[INFO] openshift.plugins ................................. SUCCESS [0.008s]
[INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [1.939s]
[INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [0.356s]
[INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [1.336s]
[INFO] org.jboss.tools.openshift.express.core ............ SUCCESS [1.573s]
[INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [3.588s]
[INFO] openshift.tests ................................... SUCCESS [0.006s]
[INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [27.663s]
[INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [28.096s]
[INFO] openshift.features ................................ SUCCESS [0.005s]
[INFO] org.jboss.tools.openshift.egit.integration.feature SUCCESS [0.204s]
[INFO] org.jboss.tools.openshift.express.feature ......... SUCCESS [0.188s]
[INFO] org.jboss.tools.openshift.egit.integration.test.feature SUCCESS [0.099s]
[INFO] org.jboss.tools.openshift.express.test.feature .... SUCCESS [0.126s]
[INFO] openshift.site .................................... SUCCESS [7.293s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
{code}
was (Author: adietish):
{code}
mvn clean verify -Dtpc.version=4.30.6.Final -Dtycho.localArtifacts=ignore
{code}
{code}
[INFO] --- repository-utils:0.16.0.CR2:generate-repository-facade (generate-facade) @ openshift.site ---
[WARNING] No org.jboss.tools.central.discovery plugin in repo. Skip generation of 'jbosstools-directory.xml'
[INFO] Building zip: /home/adietish/jboss-workspaces/jbosstools-github/jbosstools-openshift/site/target/openshift.site-2.5.1-SNAPSHOT.zip
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] openshift.all ..................................... SUCCESS [0.566s]
[INFO] openshift.plugins ................................. SUCCESS [0.008s]
[INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [1.939s]
[INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [0.356s]
[INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [1.336s]
[INFO] org.jboss.tools.openshift.express.core ............ SUCCESS [1.573s]
[INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [3.588s]
[INFO] openshift.tests ................................... SUCCESS [0.006s]
[INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [27.663s]
[INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [28.096s]
[INFO] openshift.features ................................ SUCCESS [0.005s]
[INFO] org.jboss.tools.openshift.egit.integration.feature SUCCESS [0.204s]
[INFO] org.jboss.tools.openshift.express.feature ......... SUCCESS [0.188s]
[INFO] org.jboss.tools.openshift.egit.integration.test.feature SUCCESS [0.099s]
[INFO] org.jboss.tools.openshift.express.test.feature .... SUCCESS [0.126s]
[INFO] openshift.site .................................... SUCCESS [7.293s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
{code}
> For JBIDE 4.1.1.Final: Prepare for Final/GA release [OpenShift]
> ---------------------------------------------------------------
>
> Key: JBIDE-16203
> URL: https://issues.jboss.org/browse/JBIDE-16203
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Final
>
>
> For JBIDE 4.1.1.Final [OpenShift]: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> 2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.2.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.30.6.Final
> mvn clean verify -Dtpc.version=4.31.1.Final
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16203) For JBIDE 4.1.1.Final: Prepare for Final/GA release [OpenShift]
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16203?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16203:
------------------------------------------
{code}
mvn clean verify -Dtpc.version=4.30.6.Final -Dtycho.localArtifacts=ignore
{code}
{code}
[INFO] --- repository-utils:0.16.0.CR2:generate-repository-facade (generate-facade) @ openshift.site ---
[WARNING] No org.jboss.tools.central.discovery plugin in repo. Skip generation of 'jbosstools-directory.xml'
[INFO] Building zip: /home/adietish/jboss-workspaces/jbosstools-github/jbosstools-openshift/site/target/openshift.site-2.5.1-SNAPSHOT.zip
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] openshift.all ..................................... SUCCESS [0.566s]
[INFO] openshift.plugins ................................. SUCCESS [0.008s]
[INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [1.939s]
[INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [0.356s]
[INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [1.336s]
[INFO] org.jboss.tools.openshift.express.core ............ SUCCESS [1.573s]
[INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [3.588s]
[INFO] openshift.tests ................................... SUCCESS [0.006s]
[INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [27.663s]
[INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [28.096s]
[INFO] openshift.features ................................ SUCCESS [0.005s]
[INFO] org.jboss.tools.openshift.egit.integration.feature SUCCESS [0.204s]
[INFO] org.jboss.tools.openshift.express.feature ......... SUCCESS [0.188s]
[INFO] org.jboss.tools.openshift.egit.integration.test.feature SUCCESS [0.099s]
[INFO] org.jboss.tools.openshift.express.test.feature .... SUCCESS [0.126s]
[INFO] openshift.site .................................... SUCCESS [7.293s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
{code}
> For JBIDE 4.1.1.Final: Prepare for Final/GA release [OpenShift]
> ---------------------------------------------------------------
>
> Key: JBIDE-16203
> URL: https://issues.jboss.org/browse/JBIDE-16203
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Final
>
>
> For JBIDE 4.1.1.Final [OpenShift]: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> 2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.2.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.30.6.Final
> mvn clean verify -Dtpc.version=4.31.1.Final
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16207) For JBIDE 4.1.1.Final: Prepare for Final/GA release [Webservices]
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16207?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16207:
------------------------------------------
{code}
mvn clean verify -Dtpc.version=4.30.6.Final -Dtycho.localArtifacts=ignore
{code}
{code}
[INFO] --- repository-utils:0.16.0.CR2:generate-repository-facade (generate-facade) @ openshift.site ---
[WARNING] No org.jboss.tools.central.discovery plugin in repo. Skip generation of 'jbosstools-directory.xml'
[INFO] Building zip: /home/adietish/jboss-workspaces/jbosstools-github/jbosstools-openshift/site/target/openshift.site-2.5.1-SNAPSHOT.zip
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] openshift.all ..................................... SUCCESS [0.566s]
[INFO] openshift.plugins ................................. SUCCESS [0.008s]
[INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [1.939s]
[INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [0.356s]
[INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [1.336s]
[INFO] org.jboss.tools.openshift.express.core ............ SUCCESS [1.573s]
[INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [3.588s]
[INFO] openshift.tests ................................... SUCCESS [0.006s]
[INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [27.663s]
[INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [28.096s]
[INFO] openshift.features ................................ SUCCESS [0.005s]
[INFO] org.jboss.tools.openshift.egit.integration.feature SUCCESS [0.204s]
[INFO] org.jboss.tools.openshift.express.feature ......... SUCCESS [0.188s]
[INFO] org.jboss.tools.openshift.egit.integration.test.feature SUCCESS [0.099s]
[INFO] org.jboss.tools.openshift.express.test.feature .... SUCCESS [0.126s]
[INFO] openshift.site .................................... SUCCESS [7.293s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:01.678s
[INFO] Finished at: Fri Dec 06 19:35:21 CET 2013
[INFO] Final Memory: 80M/748M
[INFO] ------------------------------------------------------------------------
{code}
> For JBIDE 4.1.1.Final: Prepare for Final/GA release [Webservices]
> -----------------------------------------------------------------
>
> Key: JBIDE-16207
> URL: https://issues.jboss.org/browse/JBIDE-16207
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Final
>
>
> For JBIDE 4.1.1.Final [Webservices]: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> 2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.2.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.30.6.Final
> mvn clean verify -Dtpc.version=4.31.1.Final
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16137) webservices component build slow during tests
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16137?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-16137:
-------------------------------------------
Interestingly... I'm seeing this (on my Windows 7 box):
{code}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
Ignoring the non-build long running job: Workbench Auto-Save Job
Ignoring the non-build long running job: Workbench Auto-Save Job
Ignoring the non-build long running job: Workbench Auto-Save Job
Ignoring the non-build long running job: Workbench Auto-Save Job
Ignoring the non-build long running job: Workbench Auto-Save Job
Ignoring the non-build long running job: Workbench Auto-Save Job
Ignoring the non-build long running job: Workbench Auto-Save Job
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] ws.all ............................................ SUCCESS [0.442s]
[INFO] ws.plugins ........................................ SUCCESS [0.007s]
[INFO] org.jboss.tools.ws.core ........................... SUCCESS [2.500s]
[INFO] org.jboss.tools.ws.creation.core .................. SUCCESS [1.791s]
[INFO] org.jboss.tools.ws.wise.ui ........................ SUCCESS [2.907s]
[INFO] org.jboss.tools.ws.ui ............................. SUCCESS [3.466s]
[INFO] org.jboss.tools.ws.creation.ui .................... SUCCESS [1.444s]
[INFO] org.jboss.tools.ws.jaxrs.core ..................... SUCCESS [1.791s]
[INFO] org.jboss.tools.ws.jaxrs.ui ....................... SUCCESS [1.491s]
[INFO] ws.tests .......................................... SUCCESS [0.006s]
[INFO] org.jboss.tools.ws.core.test ...................... SUCCESS [35.929s]
[INFO] org.jboss.tools.ws.creation.core.test ............. FAILURE [1:00:56.771s]
[INFO] org.jboss.tools.ws.ui.test ........................ SKIPPED
[INFO] org.jboss.tools.ws.jaxrs.core.test ................ SKIPPED
[INFO] ws.features ....................................... SKIPPED
[INFO] org.jboss.tools.ws.feature ........................ SKIPPED
[INFO] org.jboss.tools.ws.jaxrs.feature .................. SKIPPED
[INFO] org.jboss.tools.ws.test.feature ................... SKIPPED
[INFO] ws.site ........................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:02:31.779s
[INFO] Finished at: Fri Dec 06 11:22:25 MST 2013
[INFO] Final Memory: 64M/163M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.19.0:test (default-test) on project org.jboss.tools.ws.creation.core.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 1]
{code}
> webservices component build slow during tests
> ---------------------------------------------
>
> Key: JBIDE-16137
> URL: https://issues.jboss.org/browse/JBIDE-16137
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, webservices
> Affects Versions: 4.2.0.Alpha1
> Environment: Luna 4.4 M3 TP
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Attachments: jstack-43357.txt
>
>
> when reaching the tests on org.jboss.tools.ws.creation.core.tests, a workbench window appears but nothing is drawn and the build is *very* slow
> {code}
> [INFO] Command line:
> /bin/sh -c cd /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test && /Library/Java/JavaVirtualMachines/jdk1.7.0_12.jdk/Contents/Home/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=macosx -Dosgi.ws=cocoa -Dosgi.arch=x86_64 '-javaagent:/Users/xcoulon/.m2/repository/org/jacoco/org.jacoco.agent/0.6.1.201212231917/org.jacoco.agent-0.6.1.201212231917-runtime.jar=destfile=/Users/xcoulon/code/jbosstools/jbosstools-webservices/target/jacoco.exec,append=true,includes=org.jboss.tools.ws.creation.core*' -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -XstartOnFirstThread '-Djbosstools.test.jre.6=${jbosstools.test.jre.6}' '-Djbosstools.test.jre.5=${jbosstools.test.jre.5}' -Djbosstools.test.jboss.home.4.2=/Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/requirements/jboss-4.2.3.GA -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=true -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true -Dosgi.clean=true -jar /Users/xcoulon/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.0.v20130327-1440/org.eclipse.equinox.launcher-1.3.0.v20130327-1440.jar -data /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data -install /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work -configuration /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/configuration -application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/surefire.properties
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> {code}
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16235) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JavaEE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16235?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-16235.
------------------------------------
Resolution: Done
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JavaEE]
> -----------------------------------------------------
>
> Key: JBIDE-16235
> URL: https://issues.jboss.org/browse/JBIDE-16235
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi, cdi-extensions, jsf, seam2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [JavaEE]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 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.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha1x
> git push origin jbosstools-4.2.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16235) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JavaEE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16235?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-16235.
----------------------------------
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JavaEE]
> -----------------------------------------------------
>
> Key: JBIDE-16235
> URL: https://issues.jboss.org/browse/JBIDE-16235
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi, cdi-extensions, jsf, seam2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1 [JavaEE]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 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.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha1x
> git push origin jbosstools-4.2.0.Alpha1x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16266) NLS missing messages in SeamProjectNewWizardTest
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16266?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16266:
-----------------------------------
Fix Version/s: 4.2.0.Alpha2
> NLS missing messages in SeamProjectNewWizardTest
> -------------------------------------------------
>
> Key: JBIDE-16266
> URL: https://issues.jboss.org/browse/JBIDE-16266
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: seam2
> Affects Versions: 4.2.0.Alpha1
> Reporter: Victor Rubezhny
> Assignee: Daniel Azarov
> Priority: Trivial
> Fix For: 4.2.0.Alpha2
>
>
> When running SeamProjectNewWizardTest JUnit Test the following Warnings appear:
> {code}
> Warning: NLS missing message: JBossASAdapterInitializer_AppServer32 in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_AppServer40 in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_AppServer42 in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_AppServer50 in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_CannotCreateDriver in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_CannotCreateProfile in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_CannotCreateServer in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_JBossASHypersonicEmbeddedDB in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_Runtime in: org.jboss.tools.jst.firstrun.messages
> {code}
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16137) webservices component build slow during tests on Luna TP
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16137?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-16137:
----------------------------------
Summary: webservices component build slow during tests on Luna TP (was: webservices component build slow during tests on MacOSX 10.7)
> webservices component build slow during tests on Luna TP
> --------------------------------------------------------
>
> Key: JBIDE-16137
> URL: https://issues.jboss.org/browse/JBIDE-16137
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, webservices
> Affects Versions: 4.2.0.Alpha1
> Environment: Luna 4.4 M3 TP
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Attachments: jstack-43357.txt
>
>
> when reaching the tests on org.jboss.tools.ws.creation.core.tests, a workbench window appears but nothing is drawn and the build is *very* slow
> {code}
> [INFO] Command line:
> /bin/sh -c cd /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test && /Library/Java/JavaVirtualMachines/jdk1.7.0_12.jdk/Contents/Home/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=macosx -Dosgi.ws=cocoa -Dosgi.arch=x86_64 '-javaagent:/Users/xcoulon/.m2/repository/org/jacoco/org.jacoco.agent/0.6.1.201212231917/org.jacoco.agent-0.6.1.201212231917-runtime.jar=destfile=/Users/xcoulon/code/jbosstools/jbosstools-webservices/target/jacoco.exec,append=true,includes=org.jboss.tools.ws.creation.core*' -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -XstartOnFirstThread '-Djbosstools.test.jre.6=${jbosstools.test.jre.6}' '-Djbosstools.test.jre.5=${jbosstools.test.jre.5}' -Djbosstools.test.jboss.home.4.2=/Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/requirements/jboss-4.2.3.GA -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=true -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true -Dosgi.clean=true -jar /Users/xcoulon/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.0.v20130327-1440/org.eclipse.equinox.launcher-1.3.0.v20130327-1440.jar -data /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data -install /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work -configuration /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/configuration -application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/surefire.properties
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> {code}
--
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
12 years, 4 months
[JBoss JIRA] (JBIDE-16266) NLS missing messages in SeamProjectNewWizardTest
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16266?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-16266:
--------------------------------------
Assignee: Daniel Azarov
> NLS missing messages in SeamProjectNewWizardTest
> -------------------------------------------------
>
> Key: JBIDE-16266
> URL: https://issues.jboss.org/browse/JBIDE-16266
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: seam2
> Affects Versions: 4.2.0.Alpha1
> Reporter: Victor Rubezhny
> Assignee: Daniel Azarov
> Priority: Trivial
>
> When running SeamProjectNewWizardTest JUnit Test the following Warnings appear:
> {code}
> Warning: NLS missing message: JBossASAdapterInitializer_AppServer32 in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_AppServer40 in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_AppServer42 in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_AppServer50 in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_CannotCreateDriver in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_CannotCreateProfile in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_CannotCreateServer in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_JBossASHypersonicEmbeddedDB in: org.jboss.tools.jst.firstrun.messages
> Warning: NLS missing message: JBossASAdapterInitializer_Runtime in: org.jboss.tools.jst.firstrun.messages
> {code}
--
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
12 years, 4 months