June 2013 - jbosstools-dev - Jboss List Archives

ACTION REQUIRED: core Beta2 branch/codefreeze Thursday - steps inside

by Max Rydahl Andersen

Hi core-compnent leads, Thursday 13th is branch/codefreeze day as planned [1]. Special Note: Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main line of defense/attack on this codefreeze. A quick reminder what branch/codefreeze means for each component/repo owner: 0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira. 1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools parent. Should look something like this: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.1.0.Beta2-SNAPSHOT</version> </parent> 2) Make sure your component builds and passes its tests when run locally. $ mvn clean verify 3) Make a branch for the Beta2 builds to use. Most components uses master, thus the steps would be something like: $ git checkout master $ git pull origin master $ git checkout -b jbosstools-4.1.0.Beta2x $ git push origin jbosstools-4.1.0.Beta2x 4) Respond to this mail before end of Thursday with a "All Done for component: <your component>" or "<your component> cannot branch/freeze today because of <jira issues> must be done first" Thank you! [1] https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...

11 years, 10 months

15
18
0 / 0

Beta2 build status :: RED!

by Nick Boldt

== BLOCKER == Broken due to missing Beta2x branch: https://github.com/jbosstools/jbosstools-webservices/tree/jbosstools-4.1.... https://github.com/jbosstools/jbosstools-arquillian/tree/jbosstools-4.1.0... == URGENT == Red/yellow builds (test failures/timeouts): Base - 22 test failures Central - 1 test failure Hibernate - 1 timeout JST - 4 timeouts == HOPEFULLY FINE ONCE RESPUN == Broken due to process: JavaEE - missing upstream, respinning now Portlet - missing upstream, respinning now VPE - missing upstream, respinning now -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 10 months

4
6
0 / 0

JBoss Tools Core 4.1.0.Beta2 bits available for QE testing

by Nick Boldt

As always, these are not FINAL bits, but preliminary results for QE testing. Not for redistribution to customers. Target Platform: Add this URL to your Eclipse before attempting to install JBoss Tools, in order to resolve all dependencies. http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... Update Sites: http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.Beta2.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.Beta2.webto... Builds: http://download.jboss.org/jbosstools/builds/development/4.1.0.Beta2.core/... http://download.jboss.org/jbosstools/builds/development/4.1.0.Beta2.webto... JBoss Central: To test this version of Central, add this to your eclipse.ini file after the -vmargs line: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/development/4.1.0.Beta2/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.1.0.Beta2/ -- New + Noteworthy: Subject to change, the latest N&N is here: http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstoo... and http://docs.jboss.org/tools/whatsnew/ -- Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug... -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 10 months

1
0
0 / 0

Release of Target Platform 4.30.5.Alpha6

by Mickael Istria

Hi all, As we're approaching code freeze, I'd like to make a release of 4.30.5.Alpha6 target platform. This TP will be used to build JBoss Tools 4.1.0.Beta2. Does anyone have an objection about this. It seems that currently TP 4.30.5.Alpha6-SNAPSHOT makes everything work fine so it looks good. But maybe you have noticed some things that require more testing before we release it? Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>

11 years, 10 months

1
1
0 / 0

ACTION REQUIRED for Server, Javaee, Central: failing tests in master branch / please fix for Beta2 code freeze

by Nick Boldt

The following projects are red in Jenkins due to test timeouts: Server: [INFO] org.jboss.ide.eclipse.archives.test ............... FAILURE [40:05.535s] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.0:test (default-test) on project org.jboss.ide.eclipse.archives.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 2400 seconds -> [Help 1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Javaee: 19:02:51 [INFO] org.jboss.tools.jsf.ui.test ....................... FAILURE [1:00:15.201s] 19:02:52 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.0:test (default-test) on project org.jboss.tools.jsf.ui.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] http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... Central: [INFO] org.jboss.tools.maven.sourcelookup.test ........... FAILURE [40:17.222s] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.0:test (default-test) on project org.jboss.tools.maven.sourcelookup.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 2400 seconds -> [Help 1] http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... -- If your project is listed above, please open a JIRA against yourself to track this problem. If your project is NOT listed, but you're yellow due to test failures (or skipped tests)... please fix those too! -- Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red Hat, Inc. http://nick.divbyzero.com

11 years, 10 months

3
6
0 / 0

Re: [jbosstools-dev] ACTION REQUIRED for Server, Javaee, Central: failing tests in master branch / please fix for Beta2 code freeze

by Victor Rubezhny

jbosstools-javaee has: - known test failure in seam: https://issues.jboss.org/browse/JBIDE-14105 - a timed out test in JSF UI (JsfUiAllTests) - it occurs from time to time on my environment (tonight it was reproduced) Also, it looks like there still is a problem with Workbench Auto-Save Job: The option -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true that is included into command line is not respected by Eclipse RC3 for some reason or works not as expected. Even having such option in the command line we still have this never-ending job running: Regards, Victor On 06/13/2013 02:22 AM, Denis Golovin wrote: > On 06/12/2013 03:18 PM, Denis Golovin wrote: >> On 06/12/2013 12:54 PM, Nick Boldt wrote: >>> The following projects are red in Jenkins due to test timeouts: >>> >>> Server: >>> >>> [INFO] org.jboss.ide.eclipse.archives.test ............... FAILURE [40:05.535s] >>> [ERROR] Failed to execute goal >>> org.eclipse.tycho:tycho-surefire-plugin:0.18.0:test (default-test) on >>> project org.jboss.ide.eclipse.archives.test: Error while executing >>> platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: >>> Error while executing external command, process killed. Process >>> timeout out after 2400 seconds -> [Help 1] >>> >>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >> Changed configuration to use XVnc and that helped. But results look >> weird. In log >> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >> is says for severl test plugins >> >> [ERROR] There are test failures. >> >> >> but in the end it shows >> >> [INFO] Reactor Summary: >> [INFO] >> [INFO] archives.tests .................................... SUCCESS [0.393s] >> [INFO] org.jboss.ide.eclipse.archives.test ............... SUCCESS [50.395s] >> [INFO] org.jboss.ide.eclipse.archives.ui.test ............ SUCCESS [15.450s] >> [INFO] jmx.tests ......................................... SUCCESS [0.005s] >> [INFO] org.jboss.tools.jmx.core.test ..................... SUCCESS [21.032s] >> [INFO] as.tests .......................................... SUCCESS [0.005s] >> [INFO] org.jboss.tools.as.test.core ...................... SUCCESS [11:46.553s] >> [INFO] org.jboss.ide.eclipse.as.archives.integration.test SUCCESS [1:04.715s] >> [INFO] org.jboss.ide.eclipse.as.management.as7.tests ..... SUCCESS [3:49.784s] >> [INFO] org.jboss.ide.eclipse.as.test ..................... SUCCESS [17.708s] >> [INFO] org.jboss.ide.eclipse.as.ui.test .................. SUCCESS [25.602s] >> [INFO] org.jboss.tools.jmx.ui.test ....................... SUCCESS [6.418s] >> [INFO] server.all.tests .................................. SUCCESS [0.004s] >> [INFO] ------------------------------------------------------------------------ >> >> And build marked as unstable. >> >> >>> Javaee: >>> >>> 19:02:51 [INFO] org.jboss.tools.jsf.ui.test ....................... >>> FAILURE [1:00:15.201s] >>> >>> 19:02:52 [ERROR] Failed to execute goal >>> org.eclipse.tycho:tycho-surefire-plugin:0.18.0:test (default-test) on >>> project org.jboss.tools.jsf.ui.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] >>> >>> http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... >> >> Back to be running again, but seems to have test errors >> >> [ERROR] There are test failures. > > The same problem with reactor summary as in server. There are test > failures but reactor summary says everything was build successfully. > Does it smell like tycho 0.18.0 issue? > > >> >> >>> Central: >>> >>> [INFO] org.jboss.tools.maven.sourcelookup.test ........... FAILURE [40:17.222s] >>> >>> [ERROR] Failed to execute goal >>> org.eclipse.tycho:tycho-surefire-plugin:0.18.0:test (default-test) on >>> project org.jboss.tools.maven.sourcelookup.test: Error while executing >>> platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: >>> Error while executing external command, process killed. Process >>> timeout out after 2400 seconds -> [Help 1] >>> >>> http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... >> >> Configured to use Xvnc and seems to be all blue again. >> >> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >> >>> -- >>> >>> If your project is listed above, please open a JIRA against yourself >>> to track this problem. If your project is NOT listed, but you're >>> yellow due to test failures (or skipped tests)... please fix those >>> too! >>> >> >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev

11 years, 10 months

1
0
0 / 0

JBoss Tools Core 4.1.0.Beta1b bits available for QE testing

by Nick Boldt

As always, these are not FINAL bits, but preliminary results for QE testing. Not for redistribution to customers. Target Platform: Add this URL to your Eclipse before attempting to install JBoss Tools, in order to resolve all dependencies. http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... Update Sites: http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.Beta1b.core/ http://download.jboss.org/jbosstools/updates/JBossTools-4.1.0.Beta1b.webt... Builds: http://download.jboss.org/jbosstools/builds/development/4.1.0.Beta1b.core... http://download.jboss.org/jbosstools/builds/development/4.1.0.Beta1b.webt... JBoss Central: To test this version of Central, add this to your eclipse.ini file after the -vmargs line: -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/development/4.1.0.Beta1b/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/development/4.1.0.Beta1b/ -- New + Noteworthy: Subject to change, the latest N&N is here: http://htmlpreview.github.com/?https://raw.github.com/jbosstools/jbosstoo... and http://docs.jboss.org/tools/whatsnew/ -- Schedule / Upcoming Releases: https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug... Changes prompting this respin-b are: https://issues.jboss.org/issues/?jql=labels%20in%20%28%22respin-b%22%29%2... -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 10 months

2
2
0 / 0

Upcoming changes in Target Platform: Kepler RC3

by Mickael Istria

Hi all, I'll start the process of updating target platform to Kepler RC3 to spot some potential changes in Kepler that could affect us. This should also help to fix JBIDE-13989 (by the way, is there an automated test that reproduce this issue so we can make sure moving to Kepler fixes it?). If you have some specific requirements out of this move to Kepler RC3, please open Jiras right now. The version of target platform won't change and will remain 4.30.5.Alpha6-SNAPSHOT for now. First, I'm going to mirror the newer sites of our dependencies. Then I'll propose a PR for review (mainly by Nick if he finds time at JUDCon), it's the right rime for you to have a look if you're curious about some changes in your dependencies. Hopefully, I'll be allowed to merge it soon, so we'll get feedback from CI early enough to spot issues before we branch. Cheers. -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>

11 years, 10 months

3
6
0 / 0

URGENT: Please update reference parent pom to 4.1.0.Beta2-SNAPSHOT

by Mickael Istria

Hi all, Many components still reference parent pom 4.1.0.Beta1-SNAPSHOT which reference the repositories for JBT 4.1.0.Beta1. Some refactoring in the jbosstools-base component have happened recently (renaming of httpclient bundle, introduction of the "foundation" module) and it is important that you build against these changes. In order to do so, you NEED TO change reference to parent pom in your component to use 4.1.0.Beta2-SNAPSHOT AS SOON AS POSSIBLE. This will make CI bluer and overall quality better. From a build maintenance POV, this shows we have to think of a better way to handle how we reference repositories in parent pom and how we should not change those URLs. Brainstorming in progress.... Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>

11 years, 10 months

2
2
0 / 0

Building forge from master fails to resolve org.jboss.forge.addon:addons:jar:forge-addon:2.0.0-SNAPSHOT

by Denis Golovin

I am trying to do local build for JBoss Tools and I cannot build forge component it always fails on forge2 runtime plug-in. [ERROR] Failed to execute goal org.jboss.forge:forge-maven-plugin:1.0.0.Alpha4:addon-install (deploy-addons) on project org.jboss.tools.forge2.runtime: Execution deploy-addons of goal org.jboss.forge:forge-maven-plugin:1.0.0.Alpha4:addon-install failed: Could not resolve dependencies for addon [org.jboss.forge.addon:addons:jar:forge-addon:2.0.0-SNAPSHOT]: Could not find artifact org.jboss.forge.addon:addons:jar:forge-addon:2.0.0-SNAPSHOT Addon seems to be deployed correctly in snapshot repository and works fine as declared dependency <dependencies> <dependency> <groupId>org.jboss.forge.addon</groupId> <artifactId>addons</artifactId> <version>${version.forge}</version> <classifier>forge-addon</classifier> </dependency> </dependencies> Running mvn dependency:go-offline gives successful build with output .... [INFO] --- maven-dependency-plugin:2.4:go-offline (default-cli) @ org.jboss.tools.forge2.runtime --- [INFO] Resolved: addons-2.0.0-SNAPSHOT-forge-addon.jar [INFO] Resolved: addons-api-2.0.0-SNAPSHOT.jar [INFO] Resolved: addons-impl-2.0.0-SNAPSHOT.jar [INFO] Resolved: ui-2.0.0-SNAPSHOT-forge-addon.jar [INFO] Resolved: ui-api-2.0.0-SNAPSHOT.jar [INFO] Resolved: ui-impl-2.0.0-SNAPSHOT.jar [INFO] Resolved: convert-2.0.0-SNAPSHOT-forge-addon.jar [INFO] Resolved: convert-api-2.0.0-SNAPSHOT.jar [INFO] Resolved: convert-impl-2.0.0-SNAPSHOT.jar [INFO] Resolved: facets-2.0.0-SNAPSHOT-forge-addon.jar [INFO] Resolved: facets-api-2.0.0-SNAPSHOT.jar [INFO] Resolved: facets-impl-2.0.0-SNAPSHOT.jar [INFO] Resolved: ui-spi-2.0.0-SNAPSHOT-forge-addon.jar [INFO] Resolved: maven-2.0.0-SNAPSHOT-forge-addon.jar [INFO] Resolved: maven-api-2.0.0-SNAPSHOT.jar [INFO] Resolved: maven-model-3.0.5.jar [INFO] Resolved: plexus-utils-2.0.6.jar [INFO] Resolved: maven-impl-2.0.0-SNAPSHOT.jar [INFO] Resolved: xml-parser-1.0.0.Final.jar [INFO] Resolved: shrinkwrap-resolver-impl-maven-2.0.0-beta-3.jar [INFO] Resolved: shrinkwrap-resolver-api-maven-2.0.0-beta-3.jar [INFO] Resolved: shrinkwrap-resolver-api-2.0.0-beta-3.jar [INFO] Resolved: shrinkwrap-resolver-spi-maven-2.0.0-beta-3.jar [INFO] Resolved: shrinkwrap-resolver-spi-2.0.0-beta-3.jar [INFO] Resolved: aether-api-1.13.1.jar [INFO] Resolved: aether-impl-1.13.1.jar [INFO] Resolved: aether-spi-1.13.1.jar [INFO] Resolved: aether-util-1.13.1.jar [INFO] Resolved: aether-connector-wagon-1.13.1.jar [INFO] Resolved: maven-aether-provider-3.0.5.jar [INFO] Resolved: maven-model-builder-3.0.5.jar [INFO] Resolved: maven-repository-metadata-3.0.5.jar [INFO] Resolved: maven-settings-3.0.5.jar [INFO] Resolved: maven-settings-builder-3.0.5.jar [INFO] Resolved: plexus-interpolation-1.14.jar [INFO] Resolved: wagon-provider-api-2.4.jar [INFO] Resolved: wagon-file-2.4.jar [INFO] Resolved: wagon-http-lightweight-2.4.jar [INFO] Resolved: wagon-http-shared4-2.4.jar [INFO] Resolved: jsoup-1.7.1.jar [INFO] Resolved: httpcore-4.2.3.jar [INFO] Resolved: commons-io-2.0.1.jar [INFO] Resolved: maven-impl-projects-2.0.0-SNAPSHOT.jar [INFO] Resolved: maven-core-3.0.5.jar [INFO] Resolved: maven-artifact-3.0.5.jar [INFO] Resolved: maven-plugin-api-3.0.5.jar [INFO] Resolved: sisu-inject-plexus-2.3.0.jar [INFO] Resolved: sisu-inject-bean-2.3.0.jar [INFO] Resolved: sisu-guice-3.1.0-no_aop.jar [INFO] Resolved: plexus-classworlds-2.4.jar [INFO] Resolved: plexus-component-annotations-1.5.5.jar [INFO] Resolved: plexus-sec-dispatcher-1.3.jar [INFO] Resolved: maven-compat-3.0.5.jar [INFO] Resolved: maven-embedder-3.0.5.jar [INFO] Resolved: plexus-cipher-1.7.jar [INFO] Resolved: commons-cli-1.2.jar [INFO] Resolved: environment-2.0.0-SNAPSHOT-forge-addon.jar [INFO] Resolved: environment-api-2.0.0-SNAPSHOT.jar [INFO] Resolved: environment-impl-2.0.0-SNAPSHOT.jar [INFO] Resolved: resources-2.0.0-SNAPSHOT-forge-addon.jar [INFO] Resolved: resources-api-2.0.0-SNAPSHOT.jar [INFO] Resolved: resources-impl-2.0.0-SNAPSHOT.jar [INFO] Resolved: dependencies-2.0.0-SNAPSHOT-forge-addon.jar [INFO] Resolved: dependencies-api-2.0.0-SNAPSHOT.jar [INFO] Resolved: dependencies-impl-2.0.0-SNAPSHOT.jar [INFO] Resolved: projects-2.0.0-SNAPSHOT-forge-addon.jar [INFO] Resolved: projects-api-2.0.0-SNAPSHOT.jar [INFO] Resolved: projects-impl-2.0.0-SNAPSHOT.jar [INFO] Resolved: parser-java-2.0.0-SNAPSHOT-forge-addon.jar [INFO] Resolved: parser-java-api-2.0.0-SNAPSHOT.jar [INFO] Resolved: java-parser-api-1.0.1.Final.jar [INFO] Resolved: parser-java-impl-2.0.0-SNAPSHOT.jar [INFO] Resolved: java-parser-impl-1.0.1.Final.jar [INFO] Resolved: org.eclipse.jdt.core-3.8.2.v20120814-155456.jar [INFO] Resolved: resources-3.3.0-v20070604.jar [INFO] Resolved: runtime-3.3.100-v20070530.jar [INFO] Resolved: osgi-3.4.3.R34x_v20081215-1030.jar [INFO] Resolved: common-3.3.0-v20070426.jar [INFO] Resolved: jobs-3.3.0-v20070423.jar [INFO] Resolved: preferences-3.2.100-v20070522.jar [INFO] Resolved: contenttype-3.2.100-v20070319.jar [INFO] Resolved: text-3.3.0-v20070606-0010.jar ... [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ It looks like forge2 related problem. Any idea what is going wrong here? Thanks Denis

11 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev June 2013