March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24010) build: bump plugin version to comply with baseline check

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24010?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24010: ------------------------------------- Summary: build: bump plugin version to comply with baseline check (was: org.jboss.tools.openshift.client: Version has not incremented in 4.4.x and master branches) > build: bump plugin version to comply with baseline check > -------------------------------------------------------- > > Key: JBIDE-24010 > URL: https://issues.jboss.org/browse/JBIDE-24010 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > > {code} > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines > (default) on project org.jboss.tools.openshift.client: Version have moved backwards for > (org.jboss.tools.openshift.client/3.3.2.AM1-v20170224-1533-B1868). > Baseline has 3.3.2.Final-v20170217-1414-B33) with delta: 0.0.0 > {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > Solution: upversion your client plugin or make it not use the BUILD_ALIAS in its version (so it's only got a timestamp). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24010) build: bump plugin version to comply with baseline check

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24010?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24010: ------------------------------------- Fix Version/s: 4.4.4.AM1 > build: bump plugin version to comply with baseline check > -------------------------------------------------------- > > Key: JBIDE-24010 > URL: https://issues.jboss.org/browse/JBIDE-24010 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > > {code} > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines > (default) on project org.jboss.tools.openshift.client: Version have moved backwards for > (org.jboss.tools.openshift.client/3.3.2.AM1-v20170224-1533-B1868). > Baseline has 3.3.2.Final-v20170217-1414-B33) with delta: 0.0.0 > {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > Solution: upversion your client plugin or make it not use the BUILD_ALIAS in its version (so it's only got a timestamp). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23645) Remove org.jboss.tools.ui.bot.ext from integration tests

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23645?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-23645: ---------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.3.Final) > Remove org.jboss.tools.ui.bot.ext from integration tests > -------------------------------------------------------- > > Key: JBIDE-23645 > URL: https://issues.jboss.org/browse/JBIDE-23645 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.5.0.AM1 > > > org.jboss.tools.ui.bot.ext is an old and unmaintained test library. We should find out if/what tests still use it and fix those and ultimately remove bot.ext. > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > This was previously discussed in JBIDE-23593 where I found the following tests that still use bot.ext. > I found out that some tests still use bot.ext: > {code} > $ find . -iname 'manifest.mf' -path '*/META-INF/*'|xargs grep 'ui\.bot\.ext'|sed 's/:.*//'|uniq > ./plugins/org.jboss.tools.jst.ui.bot/META-INF/MANIFEST.MF > ./plugins/org.jboss.tools.ui.bot.ext/META-INF/MANIFEST.MF > ./tests/org.jboss.tools.portlet.ui.bot.test/META-INF/MANIFEST.MF > ./tests/org.jboss.tools.seam.ui.bot.test/META-INF/MANIFEST.MF > ./tests/org.jboss.tools.ws.ui.bot.test/META-INF/MANIFEST.MF > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23636) Update supported configuration docs / test plans / platforms for jbosstools 4.4.3 / devstudio 10.3

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23636?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-23636. ----------------------------------- Resolution: Done This is done. > Update supported configuration docs / test plans / platforms for jbosstools 4.4.3 / devstudio 10.3 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23636 > URL: https://issues.jboss.org/browse/JBIDE-23636 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Supriya Bharadwaj > Labels: releasework > Fix For: 4.4.3.Final > > > It's time to review the available platforms on which we test devstudio / jbt. > Ubuntu: > We will probably want 16.04.1 LTS and 16.10, but should check https://wiki.ubuntu.com/Releases > Fedora: > We will want to support Fedora 24 and 25, but 25 currently has some issues with Wayland - JBDS-4204 among others. > Here's the support matrix document: > https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23636) Update supported configuration docs / test plans / platforms for jbosstools 4.4.3 / devstudio 10.3

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23636?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23636. --------------------------------- > Update supported configuration docs / test plans / platforms for jbosstools 4.4.3 / devstudio 10.3 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23636 > URL: https://issues.jboss.org/browse/JBIDE-23636 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Supriya Bharadwaj > Labels: releasework > Fix For: 4.4.3.Final > > > It's time to review the available platforms on which we test devstudio / jbt. > Ubuntu: > We will probably want 16.04.1 LTS and 16.10, but should check https://wiki.ubuntu.com/Releases > Fedora: > We will want to support Fedora 24 and 25, but 25 currently has some issues with Wayland - JBDS-4204 among others. > Here's the support matrix document: > https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-23285: ---------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.3.Final) > integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23285 > URL: https://issues.jboss.org/browse/JBIDE-23285 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.5.0.AM1 > > > While running the integration tests today to investigate JBDS-4077, I discovered that: > * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]: > {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final > jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code} > * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final > [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/ > So, three problems here: > a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final) > b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice. > c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1049) Do not run any runtime test as part of smoke tests

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1049?page=com.atlassian.jira.plugin... ] Tomáš Sedmík closed JBTIS-1049. ------------------------------- Resolution: Done PR was pushed to master > Do not run any runtime test as part of smoke tests > -------------------------------------------------- > > Key: JBTIS-1049 > URL: https://issues.jboss.org/browse/JBTIS-1049 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.4.1.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.4.1.Final > > > The tests in org.jboss.too.runtime.ui.bot.test takes so long due to downloading a runtime. I don't think that we need to run these tests in every smoke test build. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24014) org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24014?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24014: ------------------------------------ [~nickboldt] master has been merged but build is still on RHEL6 nodes > org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24014 > URL: https://issues.jboss.org/browse/JBIDE-24014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.5.0.AM1 > > > {code} > 02:23:37 [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.foundation.core: Version have moved backwards for (org.jboss.tools.foundation.core/1.3.3.AM1-v20170224-0218-B1387). Baseline has 1.3.3.Final-v20170217-0505-B33) with delta: 0.0.0 -> [Help 1] > {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > Solution: upversion your plugin(s)/feature(s) to a new version in 4.4.x and master branches. > Perhaps you want 1.3.4 in 4.4.x branch, and 1.3.100 in the master branch? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 March 2017