December 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-12974 at 12/23/12 4:31 PM: -------------------------------------------------------------- Building running here [0] from my fork [1] (uses this PR [2]). [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... [1] https://github.com/nickboldt/jbosstools-integration-tests/tree/JBIDE-12974_2 [2] https://github.com/jbosstools/jbosstools-integration-tests/pull/94 To run locally, you need these settings: {code} mvn clean install -P jbosstools-nightly-staging-composite-soa-tooling,multiple.target -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} Still having some problems w/ test failures in a couple test plugins, which is why I'm running with -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} ./org.jboss.ide.eclipse.as.ui.bot.test/target/surefire-reports/org.jboss.ide.eclipse.as.ui.bot.test.AllTestsSuite.txt Tests run: 48, Failures: 0, Errors: 48, Skipped: 0, Time elapsed: 493.442 sec <<< FAILURE! ./org.jboss.tools.drools.ui.bot.test/target/surefire-reports/org.jboss.tools.drools.ui.bot.test.DroolsAllBotTests.txt Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.24 sec <<< FAILURE! ./org.jboss.tools.runtime.as.ui.bot.test/target/surefire-reports/org.jboss.tools.runtime.as.ui.bot.test.ProjectTestsSuite.txt Tests run: 12, Failures: 0, Errors: 12, Skipped: 0, Time elapsed: 39.82 sec <<< FAILURE! {code} was (Author: nickboldt): Building running here [0] from my fork [1] (uses this PR [2]). [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integrati... [1] https://github.com/nickboldt/jbosstools-integration-tests/tree/JBIDE-12974_2 [2] https://github.com/jbosstools/jbosstools-integration-tests/pull/94 To run locally, you need these settings: {code} mvn clean install -P jbosstools-nightly-staging-composite-soa-tooling,multiple.target -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} Still having some problems w/ test failures in a couple test plugins, which is why I've running with -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true {code} ./org.jboss.ide.eclipse.as.ui.bot.test/target/surefire-reports/org.jboss.ide.eclipse.as.ui.bot.test.AllTestsSuite.txt Tests run: 48, Failures: 0, Errors: 48, Skipped: 0, Time elapsed: 493.442 sec <<< FAILURE! ./org.jboss.tools.drools.ui.bot.test/target/surefire-reports/org.jboss.tools.drools.ui.bot.test.DroolsAllBotTests.txt Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.24 sec <<< FAILURE! ./org.jboss.tools.runtime.as.ui.bot.test/target/surefire-reports/org.jboss.tools.runtime.as.ui.bot.test.ProjectTestsSuite.txt Tests run: 12, Failures: 0, Errors: 12, Skipped: 0, Time elapsed: 39.82 sec <<< FAILURE! {code} > add missing IUs to coretests and soatests sites > ----------------------------------------------- > > Key: JBIDE-12974 > URL: https://issues.jboss.org/browse/JBIDE-12974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > > The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content. > [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ > [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/ > Are there any other missing IUs you need on those sites? -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13337) M2E not setting "Run Java Application" classpath properly

by Pete Muir (JIRA)

Pete Muir created JBIDE-13337: --------------------------------- Summary: M2E not setting "Run Java Application" classpath properly Key: JBIDE-13337 URL: https://issues.jboss.org/browse/JBIDE-13337 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Environment: JBDS 6.0 Reporter: Pete Muir Assignee: Fred Bricon Take a look at this screencast - http://screencast.com/t/bOg9G8XqT - the dependent project is not appearing properly in the dependencies when you run the main class. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13308) Remove cascading and rename trunk jobs to follow new naming scheme

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13308?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13308 at 12/22/12 12:28 AM: --------------------------------------------------------------- Depends on getting build pipeline/flow plugins installed - JBIDE-12850. Could also benefit from http://evgeny-goldin.com/wiki/Jenkins-maven-plugin being installed in Jenkins for job creation via maven instead of by hand. was (Author: nickboldt): Depends on getting build pipeline/flow plugins installed - JBIDE-12850. > Remove cascading and rename trunk jobs to follow new naming scheme > ------------------------------------------------------------------ > > Key: JBIDE-13308 > URL: https://issues.jboss.org/browse/JBIDE-13308 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > > Unlink job by disabling cascading/blocked by upstream. That will make us able to het faster feedback and consume/depend on less Jenkins resources. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-12973) publish reddeer update site to download.jboss.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12973: ------------------------------- Assignee: Martin Malina (was: Nick Boldt) > publish reddeer update site to download.jboss.org > ------------------------------------------------- > > Key: JBIDE-12973 > URL: https://issues.jboss.org/browse/JBIDE-12973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.1.x > > > Red deer should publish nightly/development/stable update sites like other components of JBT onto download.jboss.org. > Simplest way to get a nightly build into download.jboss.org/jbosstools/builds/staging/ is to use my publish.sh [1] script as a step during your build job. > Then, if you want to copy that to a more stable URL (for a dev milestone or stable release) use this job [2]: > [1] https://svn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/ -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-12973) publish reddeer update site to download.jboss.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12973: ------------------------------------ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... is running but is having permgen issues. Maybe it needs more memory? Assuming that it completes and most of the tests are OK, you should get: * test output * jacoco coverage report * archived artifacts * published results here: http://download.jboss.org/jbosstools/builds/staging/RedDeer_master Then, when you decide you want to copy a nightly build as an integration build, dev milestone, or stable release, you can run https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/ to perform the copy. > publish reddeer update site to download.jboss.org > ------------------------------------------------- > > Key: JBIDE-12973 > URL: https://issues.jboss.org/browse/JBIDE-12973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > > Red deer should publish nightly/development/stable update sites like other components of JBT onto download.jboss.org. > Simplest way to get a nightly build into download.jboss.org/jbosstools/builds/staging/ is to use my publish.sh [1] script as a step during your build job. > Then, if you want to copy that to a more stable URL (for a dev milestone or stable release) use this job [2]: > [1] https://svn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/ -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13308) Remove cascading

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13308?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13308: ------------------------------------ Only planning to make changes in trunk for now. As part of this JIRA, we should also consider renaming jobs to be more "Max-friendly" and replace 4.0/6.0 with 4.1/7.0 in the names. [~maxandersen] if you have a suggestion for what to call the various component jobs, please feel free to place that here. {code} jbosstools-<componentName>_<version>_trunk ? jbosstools-server_1.4.100_trunk ? jbosstools-central_4.1_trunk ? {code} > Remove cascading > ---------------- > > Key: JBIDE-13308 > URL: https://issues.jboss.org/browse/JBIDE-13308 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > > Unlink job by disabling cascading/blocked by upstream. That will make us able to het faster feedback and consume/depend on less Jenkins resources. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13308) Remove cascading and rename trunk jobs to follow new naming scheme

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13308?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13308: ------------------------------- Summary: Remove cascading and rename trunk jobs to follow new naming scheme (was: Remove cascading) > Remove cascading and rename trunk jobs to follow new naming scheme > ------------------------------------------------------------------ > > Key: JBIDE-13308 > URL: https://issues.jboss.org/browse/JBIDE-13308 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > > Unlink job by disabling cascading/blocked by upstream. That will make us able to het faster feedback and consume/depend on less Jenkins resources. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13336) create target platform using Kepler dependencies

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-13336: ---------------------------------- Summary: create target platform using Kepler dependencies Key: JBIDE-13336 URL: https://issues.jboss.org/browse/JBIDE-13336 Project: Tools (JBoss Tools) Issue Type: Bug Components: target-platform Affects Versions: 4.1.0.Alpha1 Reporter: Nick Boldt Assignee: Mickael Istria Fix For: 4.1.0.Alpha1 Along with the refactoring we talked about doing in JBIDE-13232, it's time to create a new Kepler M4 target platform. I've pulled mirrors for the three largest pieces: Kepler M4, Eclipse 4.3M4, WTP 3.5M4: http://download.jboss.org/jbosstools/updates/requirements/kepler/20121221... http://download.jboss.org/jbosstools/updates/requirements/eclipse/S-4.3M4... http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5.... Do you need anything else mirrored? If so bounce this to me and I'll get the bits copied to download.jboss.org for you. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-12371) Update Eclipse Target Platform to use Graphiti 0.9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12371?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12371: ------------------------------- Assignee: Rob Cernich (was: Douglas Palmer) > Update Eclipse Target Platform to use Graphiti 0.9 > -------------------------------------------------- > > Key: JBIDE-12371 > URL: https://issues.jboss.org/browse/JBIDE-12371 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: SOA Tooling, SwitchYard, target-platform > Affects Versions: 3.3.x > Reporter: Rob Cernich > Assignee: Rob Cernich > Priority: Critical > Fix For: 4.0.0.Alpha1-SOA > > > SwitchYard loosely integrates with the Eclipse BPMN2 editor, which has recently upgraded to Graphiti 0.9. Because of this, SwitchYard could not be installed alongside the BPMN2, so SwitchYard needed to upgrade to Graphiti 0.9. This has caused the soa-tools 3.3.x aggregate build to fail because it cannot locate the Graphiti 0.9 plugins. > If SwitchYard is the only project relying on Graphiti, we can simply upgrade the target platforms for Indigo and Juno to include Graphiti 0.9. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-12371) Update Eclipse Target Platform to use Graphiti 0.9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12371?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12371: ------------------------------------ Pulled a Graphiti 0.10 mirror... can that be used instead of 0.9? http://download.jboss.org/jbosstools/updates/requirements/graphiti/0.10.0... > Update Eclipse Target Platform to use Graphiti 0.9 > -------------------------------------------------- > > Key: JBIDE-12371 > URL: https://issues.jboss.org/browse/JBIDE-12371 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: SOA Tooling, SwitchYard, target-platform > Affects Versions: 3.3.x > Reporter: Rob Cernich > Assignee: Douglas Palmer > Priority: Critical > Fix For: 4.0.0.Alpha1-SOA > > > SwitchYard loosely integrates with the Eclipse BPMN2 editor, which has recently upgraded to Graphiti 0.9. Because of this, SwitchYard could not be installed alongside the BPMN2, so SwitchYard needed to upgrade to Graphiti 0.9. This has caused the soa-tools 3.3.x aggregate build to fail because it cannot locate the Graphiti 0.9 plugins. > If SwitchYard is the only project relying on Graphiti, we can simply upgrade the target platforms for Indigo and Juno to include Graphiti 0.9. -- 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

13 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2012