March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13728) JSF facet is not enabled for maven project with seam-faces dependency

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13728?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13728: -------------------------------- Fix Version/s: 4.1.0.Beta1 (was: 4.1.0.Alpha2) > JSF facet is not enabled for maven project with seam-faces dependency > --------------------------------------------------------------------- > > Key: JBIDE-13728 > URL: https://issues.jboss.org/browse/JBIDE-13728 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, UpStream > Affects Versions: 4.1.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.1.0.Beta1 > > > see JBIDE-8755 -- 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-13728) JSF facet is not enabled for maven project with seam-faces dependency

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13728?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13728: -------------------------------- Component/s: UpStream > JSF facet is not enabled for maven project with seam-faces dependency > --------------------------------------------------------------------- > > Key: JBIDE-13728 > URL: https://issues.jboss.org/browse/JBIDE-13728 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, UpStream > Affects Versions: 4.1.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.1.0.Alpha2 > > > see JBIDE-8755 -- 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-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 updated JBIDE-13411: ----------------------------------- Component/s: Build/Releng Did you have some more clues about Tycho being so long to process? What is the actual time of test running vs time of surefire running? I'd like to investigate on the Tycho side to see whether tycho-surefire-plugin can be improved. > 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: Build/Releng, 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13306) Reduce CI usage and feedback loop

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13306?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-13306. ---------------------------------- Resolution: Done The improvements we've done seems to have worked: we have fast feedback for all jobs, and the build-flow jobs runs weekly and ensure API compatibility between components. > Reduce CI usage and feedback loop > --------------------------------- > > Key: JBIDE-13306 > URL: https://issues.jboss.org/browse/JBIDE-13306 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > We need to reduce Jenkins usage to get faster feedback. -- 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] (JBDS-1885) aggregation poms (packaging type = pom) in JBDS should be versioned 5.0.0, not 0.0.x

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-1885?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-1885: --------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 6.0.x) > aggregation poms (packaging type = pom) in JBDS should be versioned 5.0.0, not 0.0.x > ------------------------------------------------------------------------------------ > > Key: JBDS-1885 > URL: https://issues.jboss.org/browse/JBDS-1885 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 5.0.0.M3 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 7.0.0.Alpha2 > > > (As discussed via email... > Instead of > <artifactId>com.jboss.jbds.all</artifactId> > <name>com.jboss.jbds.all</name> > <version>0.0.1-SNAPSHOT</version> > or > <groupId>com.jboss.jbds</groupId> > <artifactId>product</artifactId> > <version>0.0.2-SNAPSHOT</version> > the version should be set to the current release (5.0.0-SNAPSHOT) and inherited from the root poms in product/, product-soa/, extras/, etc. -- 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] (JBDS-1885) aggregation poms (packaging type = pom) in JBDS should be versioned 5.0.0, not 0.0.x

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-1885?page=com.atlassian.jira.plugin.... ] Mickael Istria closed JBDS-1885. -------------------------------- Resolution: Done > aggregation poms (packaging type = pom) in JBDS should be versioned 5.0.0, not 0.0.x > ------------------------------------------------------------------------------------ > > Key: JBDS-1885 > URL: https://issues.jboss.org/browse/JBDS-1885 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 5.0.0.M3 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 7.0.0.Alpha2 > > > (As discussed via email... > Instead of > <artifactId>com.jboss.jbds.all</artifactId> > <name>com.jboss.jbds.all</name> > <version>0.0.1-SNAPSHOT</version> > or > <groupId>com.jboss.jbds</groupId> > <artifactId>product</artifactId> > <version>0.0.2-SNAPSHOT</version> > the version should be set to the current release (5.0.0-SNAPSHOT) and inherited from the root poms in product/, product-soa/, extras/, etc. -- 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] (JBDS-1885) aggregation poms (packaging type = pom) in JBDS should be versioned 5.0.0, not 0.0.x

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-1885?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-1885: --------------------------------- Current version of JBDS is set in JBDS pom (ie all poms are in version 7.0.0-SNAPSHOT). So we can close this ticket > aggregation poms (packaging type = pom) in JBDS should be versioned 5.0.0, not 0.0.x > ------------------------------------------------------------------------------------ > > Key: JBDS-1885 > URL: https://issues.jboss.org/browse/JBDS-1885 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 5.0.0.M3 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 6.0.x > > > (As discussed via email... > Instead of > <artifactId>com.jboss.jbds.all</artifactId> > <name>com.jboss.jbds.all</name> > <version>0.0.1-SNAPSHOT</version> > or > <groupId>com.jboss.jbds</groupId> > <artifactId>product</artifactId> > <version>0.0.2-SNAPSHOT</version> > the version should be set to the current release (5.0.0-SNAPSHOT) and inherited from the root poms in product/, product-soa/, extras/, etc. -- 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] (JBTIS-34) JBTIS - remove RUNTIME-SOA references from JBTIS

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-34: ------------------------------- Summary: JBTIS - remove RUNTIME-SOA references from JBTIS Key: JBTIS-34 URL: https://issues.jboss.org/browse/JBTIS-34 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Components: runtime-soa Affects Versions: 4.0.0 Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 4.0.0 Remove runtime SOA component references from JBTIS. -- 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-13843) SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead?

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13843?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13843: --------------------------------------- [~nickboldt] question: When will you release the new TP to http://download.jboss.org/jbosstools/updates/kepler/ ? The current version (4.30.5.Alpha) is based on M5, right? Because it still contains junit4. So I would prefer to wait for this new release before changing RedDeer to use it. > SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead? > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13843 > URL: https://issues.jboss.org/browse/JBIDE-13843 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, testing-tools > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 4.1.0.Alpha2 > > > Eclipse 4.3M5a contains: > {code}4.3milestones/S-4.3M5a-201302041400/plugins/org.junit4_4.8.1.v20120705-112236.jar{code} > But in Eclipse 4.3M6, the only JUnit available is: > {code}4.3milestones/S-4.3M6-201303141330/plugins/org.junit_4.11.0.v201303080030.jar{code} > So, we need to see if a newer SWTBot can be used which depends on org.junit instead of org.junit4. -- 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 Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-12973: ---------------------------------- Release Notes Text: (was: This JIRA can be resolved now - the job is working (thanks Nick and Mickael!). There are failures in the testsuite but that's a problem that needs to be fixed in RedDeer.) Moving resolve comment from wrong field: This JIRA can be resolved now - the job is working (thanks Nick and Mickael!). There are failures in the testsuite but that's a problem that needs to be fixed in RedDeer. > 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-tools, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.1.0.Alpha2 > > > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2013