February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23744) For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [forge]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23744?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23744. ------------------------------ Resolution: Done Closing done. > For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [forge] > --------------------------------------------------------------- > > Key: JBIDE-23744 > URL: https://issues.jboss.org/browse/JBIDE-23744 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM2 > > > For JBIDE 4.4.3.AM2 [forge]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md features plugins pom.xml pom.xml.orig site tests *{color:orange}4.4.3.AM2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23749) For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [livereload]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23749?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23749. ------------------------------ Resolution: Done Closing done. > For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [livereload] > -------------------------------------------------------------------- > > Key: JBIDE-23749 > URL: https://issues.jboss.org/browse/JBIDE-23749 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM2 > > > For JBIDE 4.4.3.AM2 [livereload]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md features plugins pom.xml pom.xml.orig site tests *{color:orange}4.4.3.AM2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for livereload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23743) For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [central]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23743?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23743. ------------------------------ Resolution: Done Closing done. > For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [central] > ----------------------------------------------------------------- > > Key: JBIDE-23743 > URL: https://issues.jboss.org/browse/JBIDE-23743 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Friendly Jira Robot > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM2 > > > For JBIDE 4.4.3.AM2 [central]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md all-tests central discovery examples maven pom.xml pom.xml.orig site *{color:orange}4.4.3.AM2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23828) Move jst.reddeer plugin from integration-tests to eclipse (upstream)

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-23828: ---------------------------------- Summary: Move jst.reddeer plugin from integration-tests to eclipse (upstream) Key: JBIDE-23828 URL: https://issues.jboss.org/browse/JBIDE-23828 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, jst Reporter: Pavol Srna Fix For: 4.4.3.Final refactoring / repackaging will be needed, CQ probably as well -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23827) Move docker.redder plugin from jbosstools-integration-tests to eclipse (upstream)

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-23827: ---------------------------------- Summary: Move docker.redder plugin from jbosstools-integration-tests to eclipse (upstream) Key: JBIDE-23827 URL: https://issues.jboss.org/browse/JBIDE-23827 Project: Tools (JBoss Tools) Issue Type: Task Components: docker, integration-tests Reporter: Pavol Srna Fix For: 4.4.3.Final Tracked here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=510754 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23756) Moved/Refactored AS itests have lost the possibility to run against specific eap build

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23756?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23756: --------------------------------------- I opened a followup JIRA here: JBIDE-23825 > Moved/Refactored AS itests have lost the possibility to run against specific eap build > -------------------------------------------------------------------------------------- > > Key: JBIDE-23756 > URL: https://issues.jboss.org/browse/JBIDE-23756 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, server > Reporter: Pavol Srna > Assignee: Pavol Srna > Priority: Critical > Fix For: 4.4.3.AM2 > > > AS itests have been moved to jbosstools-server component repo and refactored/optimized. > But the refactored implementation in jbosstools-server doesn't support running itests against specific EAP build (as it has in integration-tests repo), which breaks eap team compatibility jobs listed here [1] > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-JBDS/ > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-JBDS/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23825) Improve eap compatibility test execution

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23825?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-23825: ---------------------------------- Component/s: integration-tests > Improve eap compatibility test execution > ---------------------------------------- > > Key: JBIDE-23825 > URL: https://issues.jboss.org/browse/JBIDE-23825 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, server > Affects Versions: 4.4.3.AM2 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.4.3.Final > > > This is a followup of JBIDE-23756 - with that, we are once again able to execute compatibility tests for eap. But there are a few things missing: > For now I will make it work with what we have, but there are several things that need to be fixed: > 1. Even if you only run the eap7x-compatibility profile, all of the runtimes (jboss as 4, as 5, as 7, wildfly...) will be downloaded anyway, because this is set up in as/itests/pom.xml - we need to come up with a way to only do this if the compatibility profile is not active. Maybe we need to switch to profile activation by property, e.g. eap7x-compatibility - the profile in as/itests/org.jboss.tools.as.ui.bot.itests/pom.xml would be activated by this, whereas all the other runtime downloads in as/itests/pom.xml would be in a profile that is deactivated using this property. > 2. https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/org... > The eap7x-compatibility profile has jboss-eap-7.0 server directory hardcoded. You can still override the whole property with something else for eap 7.1, but it would be nice to improve this. > For reference, this is a job where Radim demonstrated the new way to execute tests: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/All/job... > And these are the two jobs EAP QE uses for the compatibilty testing: > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-70x-jbds-c... > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23825) Improve eap compatibility test execution

by Martin Malina (JIRA)

Martin Malina created JBIDE-23825: ------------------------------------- Summary: Improve eap compatibility test execution Key: JBIDE-23825 URL: https://issues.jboss.org/browse/JBIDE-23825 Project: Tools (JBoss Tools) Issue Type: Task Components: server Affects Versions: 4.4.3.AM2 Reporter: Martin Malina Assignee: Martin Malina Fix For: 4.4.3.Final This is a followup of JBIDE-23756 - with that, we are once again able to execute compatibility tests for eap. But there are a few things missing: For now I will make it work with what we have, but there are several things that need to be fixed: 1. Even if you only run the eap7x-compatibility profile, all of the runtimes (jboss as 4, as 5, as 7, wildfly...) will be downloaded anyway, because this is set up in as/itests/pom.xml - we need to come up with a way to only do this if the compatibility profile is not active. Maybe we need to switch to profile activation by property, e.g. eap7x-compatibility - the profile in as/itests/org.jboss.tools.as.ui.bot.itests/pom.xml would be activated by this, whereas all the other runtime downloads in as/itests/pom.xml would be in a profile that is deactivated using this property. 2. https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/org... The eap7x-compatibility profile has jboss-eap-7.0 server directory hardcoded. You can still override the whole property with something else for eap 7.1, but it would be nice to improve this. For reference, this is a job where Radim demonstrated the new way to execute tests: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/All/job... And these are the two jobs EAP QE uses for the compatibilty testing: https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-70x-jbds-c... https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23826) Move {batch/cdi/seam}.reddeer plugins from jbosstools-integration-tests to jbosstools-javaee

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-23826: ---------------------------------- Summary: Move {batch/cdi/seam}.reddeer plugins from jbosstools-integration-tests to jbosstools-javaee Key: JBIDE-23826 URL: https://issues.jboss.org/browse/JBIDE-23826 Project: Tools (JBoss Tools) Issue Type: Task Components: batch, cdi, integration-tests Reporter: Pavol Srna Fix For: 4.4.3.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23019) Integration tests: have them running automatically, continuously

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23019?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-23019: ------------------------------------ There was some work done [1], but a lot is still ahead of me. I wil probably leave this jira open and create subtasks for smaller chunks of work. [1] https://github.com/jbosstools/jbosstools-integration-tests/pull/1736 https://github.com/jbosstools/jbosstools-integration-tests/pull/1732 https://github.com/jbosstools/jbosstools-integration-tests/pull/1720 https://github.com/jbosstools/jbosstools-openshift/pull/1398 https://github.com/jbosstools/jbosstools-openshift/pull/1397 https://github.com/jbosstools/jbosstools-openshift/pull/1395 > Integration tests: have them running automatically, continuously > ---------------------------------------------------------------- > > Key: JBIDE-23019 > URL: https://issues.jboss.org/browse/JBIDE-23019 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Radim Hopp > Labels: integration_tests > Fix For: 4.4.3.AM2 > > > The integration tests suite is very lenghty to run and should thus be run in a continuous manner on our CI. > There are several pain-points currently: > - there's no dedicated OS instance to run them against > - tests are not stable > - etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 2017