February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13469) Add property to disable JBoss Central opening when JBT are starting

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-13469: ----------------------------------- Summary: Add property to disable JBoss Central opening when JBT are starting Key: JBIDE-13469 URL: https://issues.jboss.org/browse/JBIDE-13469 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central Affects Versions: 4.1.0.Alpha1 Reporter: Vlado Pakan Assignee: Snjezana Peco Would be nice to have property allowing to disable JBoss Central opening when JBT are started from command line. It will stabilize and speed up swt bot tests and also users which are creating a lot of workspaces are annoyed by JBoss Central displaying each time they open new workspace -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13411) JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13411: ---------------------------------------- [~dgolovin] Yes, Tycho takes time to compute classpath and build tests as well. However I'm not sure it's enough to conclude that the 8hrs are spent only by Tycho. Do you know how long takes a "mvn clean verify -DskipTests" ? This command build tests and so on, but just prevent surefire from running the test app. > JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13411 > URL: https://issues.jboss.org/browse/JBIDE-13411 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor Templates > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.1.x > > Attachments: tests-vs-tycho-build-time.png > > > On a good day, tests will run and all pass in under 4hrs. > On a grey day, tests will have failures but complete in under 6hrs. > On a bad day, tests will stall out and the job will fail when it hits its duration upper limit of 8hrs. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Surely some of these tests are: > a) integration, not unit test, and should be relocated to https://github.com/jbosstools/jbosstools-integration-tests/ and run as part of a new job like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... ? > b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution? -- 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, 2 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-12973: --------------------------------------- Another PR removing a reddeer version definition from a test's manifest. https://github.com/jbosstools/jbosstools-integration-tests/pull/145 > 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, 2 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-12973: --------------------------------------- Thanks for the info, Nick. Now that https://github.com/jbosstools/jbosstools-integration-tests/pull/142 is closed (remove reddeer repo definitions from test poms) and all the manifests that need reddeer refer to it without a version we can finally maintain the reddeer requirement easily. Actually, this was for master only. I need to check what can be done for 4.0.x - at the very least we should set a fixed version of RedDeer everywhere so it's reproducible in the future. Another PR will follow. > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13467) integration-tests site won't build after reractoring: "Missing requirement: org.jboss.tools.maven.configurators.tests 1.5.0.Alpha1-v20130124-1009-B213 requires 'bundle org.jboss.tools.maven.jpa 0.0.0' but it could not be found"

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13467?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-13467: ------------------------------------- Assignee: Fred Bricon (was: Martin Malina) Nick, note that QE is only maintaining the integration tests, i.e. those with ui.bot in the name. Assigning to Fred who I suppose is the owner of this test. > integration-tests site won't build after reractoring: "Missing requirement: org.jboss.tools.maven.configurators.tests 1.5.0.Alpha1-v20130124-1009-B213 requires 'bundle org.jboss.tools.maven.jpa 0.0.0' but it could not be found" > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13467 > URL: https://issues.jboss.org/browse/JBIDE-13467 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.1.0.Alpha1, 4.0.x > > > [ERROR] Missing requirement: org.jboss.tools.maven.configurators.tests 1.5.0.Alpha1-v20130124-1009-B213 requires 'bundle org.jboss.tools.maven.jpa 0.0.0' but it could not be found > Cause is JBIDE-13048 -- org.jboss.tools.maven.jpa is now org.eclipse.m2e.wtp.jpa. > Will need to update tests to use new namespace. > Note similar refactoring for jaxrs and jsf. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13243) Create Recursive XML Text Source Test

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13243?page=com.atlassian.jira.plugi... ] Andrej Podhradsky updated JBIDE-13243: -------------------------------------- Description: The test will include: * Importing an XML schema * Modeling recursive XML documents * Setting up a connection to a text source * Using the TEXTTABLE function to access the data in a relational fashion * Creating and deploying a VDB * Executing queries that return XML documents was: The test will include: * Importing an XML schema</li> * Modeling recursive XML documents</li> * Setting up a connection to a text source</li> * Using the TEXTTABLE function to access the data in a relational fashion</li> * Creating and deploying a VDB</li> * Executing queries that return XML documents</li> > Create Recursive XML Text Source Test > ------------------------------------- > > Key: JBIDE-13243 > URL: https://issues.jboss.org/browse/JBIDE-13243 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: QA > Environment: Teiid Designer 8.x > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > > The test will include: > * Importing an XML schema > * Modeling recursive XML documents > * Setting up a connection to a text source > * Using the TEXTTABLE function to access the data in a relational fashion > * Creating and deploying a VDB > * Executing queries that return XML documents -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-5929) Clean up, simplify, and centralize JBT/JBDS dependencies

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-5929?page=com.atlassian.jira.plugin... ] Nick Boldt updated JBIDE-5929: ------------------------------ Fix Version/s: 3.3.2 (was: 3.3.x) > Clean up, simplify, and centralize JBT/JBDS dependencies > -------------------------------------------------------- > > Key: JBIDE-5929 > URL: https://issues.jboss.org/browse/JBIDE-5929 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: Build/Releng > Affects Versions: 3.2.x > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 3.3.2 > > > 1. create document cataloguing all the deps against which we currently build - both @ Eclipse, @ JBoss, and elsewhere > 2. copy deps hosted on sourceforge & porkchop to repository.jboss > 3. clean out old deps which are no longer used (caution: we may still need a JBT 3.0.4 or JBDS 2.1.2 build) > 4. where possible, replace multiple SDKs with a single repo zip > ... > Note that repository.jboss.org is essentially read-only now, and the sync between svn and the repository.jboss.org filesystem is disabled. So... is it time to move everything to download.jboss.org? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-5929) Clean up, simplify, and centralize JBT/JBDS dependencies

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-5929?page=com.atlassian.jira.plugin... ] Nick Boldt closed JBIDE-5929. ----------------------------- Resolution: Out of Date This is entirely obsoleted by migration to Tycho/Maven for our builds. > Clean up, simplify, and centralize JBT/JBDS dependencies > -------------------------------------------------------- > > Key: JBIDE-5929 > URL: https://issues.jboss.org/browse/JBIDE-5929 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: Build/Releng > Affects Versions: 3.2.x > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 3.3.2 > > > 1. create document cataloguing all the deps against which we currently build - both @ Eclipse, @ JBoss, and elsewhere > 2. copy deps hosted on sourceforge & porkchop to repository.jboss > 3. clean out old deps which are no longer used (caution: we may still need a JBT 3.0.4 or JBDS 2.1.2 build) > 4. where possible, replace multiple SDKs with a single repo zip > ... > Note that repository.jboss.org is essentially read-only now, and the sync between svn and the repository.jboss.org filesystem is disabled. So... is it time to move everything to download.jboss.org? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13411) JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13411: ---------------------------------- Attachment: tests-vs-tycho-build-time.png > JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13411 > URL: https://issues.jboss.org/browse/JBIDE-13411 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor Templates > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.1.x > > Attachments: tests-vs-tycho-build-time.png > > > On a good day, tests will run and all pass in under 4hrs. > On a grey day, tests will have failures but complete in under 6hrs. > On a bad day, tests will stall out and the job will fail when it hits its duration upper limit of 8hrs. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Surely some of these tests are: > a) integration, not unit test, and should be relocated to https://github.com/jbosstools/jbosstools-integration-tests/ and run as part of a new job like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... ? > b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13411) JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-13411: --------------------------------------- this issue could be related to tycho 0.16.0. I was running local build and at some point noticed tycho-surefire-plugin spend more time trying to run test plugin then actual tests (see attached screenshot [^tests-vs-tycho-build-time.png]). The flat parts of the the graph for memory consumption are time whne tests are running, other are time maven spent between moments when tycho-surefire-plugin invoked and eclipse started to run tests. > JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13411 > URL: https://issues.jboss.org/browse/JBIDE-13411 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor Templates > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.1.x > > > On a good day, tests will run and all pass in under 4hrs. > On a grey day, tests will have failures but complete in under 6hrs. > On a bad day, tests will stall out and the job will fail when it hits its duration upper limit of 8hrs. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Surely some of these tests are: > a) integration, not unit test, and should be relocated to https://github.com/jbosstools/jbosstools-integration-tests/ and run as part of a new job like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... ? > b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution? -- 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, 2 months

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 February 2013