September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25007) Update 4.70.x and 4.71.x TPs to include Eclipse Red Deer 2.0.0.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25007?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25007: ------------------------------- Fix Version/s: 4.5.1.AM3 > Update 4.70.x and 4.71.x TPs to include Eclipse Red Deer 2.0.0.Final > -------------------------------------------------------------------- > > Key: JBIDE-25007 > URL: https://issues.jboss.org/browse/JBIDE-25007 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Fix For: 4.5.1.AM3 > > > After Sept 20, [~rawagner] will give me a link to the Red Deer 2.0.0.Final update site, and I will mirror it to download.jboss.org then update the 4.70.x and 4.71.x target platforms to fetch this update. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25007) Update 4.70.x and 4.71.x TPs to include Eclipse Red Deer 2.0.0.Final

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25007: ---------------------------------- Summary: Update 4.70.x and 4.71.x TPs to include Eclipse Red Deer 2.0.0.Final Key: JBIDE-25007 URL: https://issues.jboss.org/browse/JBIDE-25007 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: target-platform Affects Versions: 4.5.1.AM2 Reporter: Nick Boldt After Sept 20, [~rawagner] will give me a link to the Red Deer 2.0.0.Final update site, and I will mirror it to download.jboss.org then update the 4.70.x and 4.71.x target platforms to fetch this update. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24943) Maven: refactor integration tests for use with RedDeer 2.0

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24943?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-24943: ------------------------------------- Assignee: Josef Kopriva (was: Vojtech Prusa) > Maven: refactor integration tests for use with RedDeer 2.0 > ---------------------------------------------------------- > > Key: JBIDE-24943 > URL: https://issues.jboss.org/browse/JBIDE-24943 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, maven > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24973) update TP to include org.eclipse.m2e 1.8.1.20170728-1531

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24973?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24973 at 9/11/17 9:46 AM: ------------------------------------------------------------- Yeah, I meant 1.8.1. Updated the issue title. As to browsing Fedora / Koji for packages, here's how: 1. Search: https://koji.fedoraproject.org/koji/search?match=glob&type=package&terms=... 2. Explore: https://koji.fedoraproject.org/koji/buildinfo?buildID=953415 Fedora has 1.8.0 right now so we'll need to [get 1.8.1 built there too|https://bugzilla.redhat.com/show_bug.cgi?id=1489929] so that this dependency in devstudio rpm can be resolved from upstream rpm rather than devstudio update site. was (Author: nickboldt): Yeah, I meant 1.8.1. Updated the issue title. As to browsing Fedora / Koji for packages, here's how: 1. Search: https://koji.fedoraproject.org/koji/search?match=glob&type=package&terms=... 2. Explore: https://koji.fedoraproject.org/koji/buildinfo?buildID=953415 Fedora has 1.8.0 right now so we'll need to get 1.8.1 built there too so that this dependency in devstudio rpm can be resolved from upstream rpm rather than devstudio update site. > update TP to include org.eclipse.m2e 1.8.1.20170728-1531 > -------------------------------------------------------- > > Key: JBIDE-24973 > URL: https://issues.jboss.org/browse/JBIDE-24973 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven, target-platform > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > In Fedora, the latest o.e.m2e is 0.8.0, so we should use the same version in JBT/devstudio. > See: JBDS-4532 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24973) update TP to include org.eclipse.m2e 1.8.1.20170728-1531

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24973?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24973: ------------------------------------ Yeah, I meant 1.8.1. Updated the issue title. As to browsing Fedora / Koji for packages, here's how: 1. Search: https://koji.fedoraproject.org/koji/search?match=glob&type=package&terms=... 2. Explore: https://koji.fedoraproject.org/koji/buildinfo?buildID=953415 Fedora has 1.8.0 right now so we'll need to get 1.8.1 built there too so that this dependency in devstudio rpm can be resolved from upstream rpm rather than devstudio update site. > update TP to include org.eclipse.m2e 1.8.1.20170728-1531 > -------------------------------------------------------- > > Key: JBIDE-24973 > URL: https://issues.jboss.org/browse/JBIDE-24973 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven, target-platform > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > In Fedora, the latest o.e.m2e is 0.8.0, so we should use the same version in JBT/devstudio. > See: JBDS-4532 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24973) update TP to include org.eclipse.m2e 1.8.1.20170728-1531

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24973?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24973: ------------------------------- Summary: update TP to include org.eclipse.m2e 1.8.1.20170728-1531 (was: update TP to include org.eclipse.m2e 0.8.0 (currently 0.7.1)) > update TP to include org.eclipse.m2e 1.8.1.20170728-1531 > -------------------------------------------------------- > > Key: JBIDE-24973 > URL: https://issues.jboss.org/browse/JBIDE-24973 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven, target-platform > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > In Fedora, the latest o.e.m2e is 0.8.0, so we should use the same version in JBT/devstudio. > See: JBDS-4532 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25003) test failure in org.jboss.tools.common.model.ui.test - need to move to Eclipse Red Deer 2.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25003?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25003: ------------------------------------ Generally we build against the minimum compatible Eclipse version (Oxygen.0) and run tests against the latest (Oxygen.1). So the options here are to * build a new 4.70.3.AM2-SNAPSHOT target platform which is Oxygen.0 + Red Deer 2.0.0.Beta, or * set the MIN TP to the Oxygen.1 version. > test failure in org.jboss.tools.common.model.ui.test - need to move to Eclipse Red Deer 2.0 > ------------------------------------------------------------------------------------------- > > Key: JBIDE-25003 > URL: https://issues.jboss.org/browse/JBIDE-25003 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.1.AM2 > > Attachments: jbide25003.compilation.failures.txt, whatwhat.txt > > > {code}21:20:59 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on > project org.jboss.tools.common.model.ui.test: An unexpected error occured while launching the test runtime > (return code 13). See log for details. -> [Help 1] > {code} > -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > See also .log: [^whatwhat.txt] > -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24798) Testing: ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24798?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24798: ------------------------------------ Thanks for updating the job description. I fixed the link from http://tools.jboss.org/downloads/jbosstools/oxygen/4.5.x.Nightly.html#zips but didn't see that the job linked to the old namespace. > Testing: ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata) > ---------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24798 > URL: https://issues.jboss.org/browse/JBIDE-24798 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, build, updatesite > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.5.1.AM2 > > > After 4.5.0.Final is done, I need to ensure that browsersim zip is published to nexus AND its update site is not corrupted (missing artifacts like browsersim.eclipse in the metadata). > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Possible solution is to run *mvn install -f products/pom.xml*, then *cd products/browsersim-standalone; mvn deploy -Pdeploy-to-jboss.org ...* > Also need to update link on http://tools.jboss.org/downloads/jbosstools/oxygen/4.5.x.Nightly.html#zips to 3.8.100, not 3.8.4 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25006) ITests profile is active by default

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25006?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-25006: ---------------------------------- Description: The intention is that if you run a build of anything depending on the parent pom, by default ITests profile is not active. But this doesn't work and it's always active unless you set -DskipITests=true from command line. The parent pom sets <skipITests>true</skipITests> here: https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... And the ITests profile is activated if the skipITests property is not set at all: https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... {code} <activation> <property> <name>!skipITests</name> </property> </activation> {code} We assumed that this would work but it turns out it does not work because profile activation only works with system properties and not properties in a pom. Pavol suggests simply removing the activation clause for that profile. [~nickboldt], what do you think of that? It seems simple enough. But who knows if there's hidden consequences to jobs that are used to the current behavior. Context: Builds of different repos started failing for us. Target platform max contains new RedDeer 2.0 and plugins in master still require RedDeer 1.x which is in target platform min. But it turned out that tpc.version is always set to target platform max which is not expected. So when investigating, we found that once the ITests profile is activated, it will set the tpc.version to max. This build breakage will disappear once TARGET_PLATFORM_VERSION_MIN is updated to the same version as TARGET_PLATFORM_VERSION_MAX - which is needed after the reddeer upgrade to 2.0. This is discussed in [1]. But we should still fix this. [1] https://issues.jboss.org/browse/JBIDE-25003?focusedCommentId=13461627&pag... Cc: [~psrna] was: The intention is that if you run a build of anything depending on the parent pom [1], by default ITests profile is not active. But this doesn't work and it's always active unless you set -DskipITests=true from command line. The parent pom sets <skipITests>true</skipITests> here: https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... And the ITests profile is activated if the skipITests property is not set at all: https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... {code} <activation> <property> <name>!skipITests</name> </property> </activation> {code} We assumed that this would work but it turns out it does not work because profile activation only works with system properties and not properties in a pom. Pavol suggests simply removing the activation clause for that profile. [~nickboldt], what do you think of that? It seems simple enough. But who knows if there's hidden consequences to jobs that are used to the current behavior. Context: Builds of different repos started failing for us. Target platform max contains new RedDeer 2.0 and plugins in master still require RedDeer 1.x which is in target platform min. But it turned out that tpc.version is always set to target platform max which is not expected. So when investigating, we found that once the ITests profile is activated, it will set the tpc.version to max. This build breakage will disappear once TARGET_PLATFORM_VERSION_MIN is updated to the same version as TARGET_PLATFORM_VERSION_MAX - which is needed after the reddeer upgrade to 2.0. But we should still fix this. Cc: [~psrna] > ITests profile is active by default > ----------------------------------- > > Key: JBIDE-25006 > URL: https://issues.jboss.org/browse/JBIDE-25006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > The intention is that if you run a build of anything depending on the parent pom, by default ITests profile is not active. But this doesn't work and it's always active unless you set -DskipITests=true from command line. > The parent pom sets <skipITests>true</skipITests> here: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > And the ITests profile is activated if the skipITests property is not set at all: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > {code} > <activation> > <property> > <name>!skipITests</name> > </property> > </activation> > {code} > We assumed that this would work but it turns out it does not work because profile activation only works with system properties and not properties in a pom. > Pavol suggests simply removing the activation clause for that profile. > [~nickboldt], what do you think of that? It seems simple enough. But who knows if there's hidden consequences to jobs that are used to the current behavior. > Context: Builds of different repos started failing for us. Target platform max contains new RedDeer 2.0 and plugins in master still require RedDeer 1.x which is in target platform min. But it turned out that tpc.version is always set to target platform max which is not expected. So when investigating, we found that once the ITests profile is activated, it will set the tpc.version to max. > This build breakage will disappear once TARGET_PLATFORM_VERSION_MIN is updated to the same version as TARGET_PLATFORM_VERSION_MAX - which is needed after the reddeer upgrade to 2.0. This is discussed in [1]. But we should still fix this. > [1] https://issues.jboss.org/browse/JBIDE-25003?focusedCommentId=13461627&pag... > Cc: [~psrna] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25006) ITests profile is active by default

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25006?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-25006: ---------------------------------- Description: The intention is that if you run a build of anything depending on the parent pom [1], by default ITests profile is not active. But this doesn't work and it's always active unless you set -DskipITests=true from command line. The parent pom sets <skipITests>true</skipITests> here: https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... And the ITests profile is activated if the skipITests property is not set at all: https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... {code} <activation> <property> <name>!skipITests</name> </property> </activation> {code} We assumed that this would work but it turns out it does not work because profile activation only works with system properties and not properties in a pom. Pavol suggests simply removing the activation clause for that profile. [~nickboldt], what do you think of that? It seems simple enough. But who knows if there's hidden consequences to jobs that are used to the current behavior. Context: Builds of different repos started failing for us. Target platform max contains new RedDeer 2.0 and plugins in master still require RedDeer 1.x which is in target platform min. But it turned out that tpc.version is always set to target platform max which is not expected. So when investigating, we found that once the ITests profile is activated, it will set the tpc.version to max. This build breakage will disappear once TARGET_PLATFORM_VERSION_MIN is updated to the same version as TARGET_PLATFORM_VERSION_MAX - which is needed after the reddeer upgrade to 2.0. But we should still fix this. Cc: [~psrna] was: The intention is that if you run a build of anything depending on the parent pom [1], by default ITests profile is not active. But this doesn't work and it's always active unless you set -DskipITests=true from command line. The parent pom sets <skipITests>true</skipITests> here: https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... And the ITests profile is activated if the skipITests property is not set at all: https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... {code} <activation> <property> <name>!skipITests</name> </property> </activation> {code} We assumed that this would work but it turns out it does not work because profile activation only works with system properties and not properties in a pom. Pavol suggests simply removing the activation clause for that profile. [~nickboldt], what do you think of that? It seems simple enough. But who knows if there's hidden consequences to jobs that are used to the current behavior. Context: Builds of different repos started failing for us. Target platform max contains new RedDeer 2.0 and plugins in master still require RedDeer 1.x which is in target platform min. But it turned out that tpc.version is always set to target platform max which is not expected. So when investigating, we found that once the ITests profile is activated, it will set the tpc.version to max. This build breakage will disappear once TARGET_PLATFORM_VERSION_MIN is updated to the same version as TARGET_PLATFORM_VERSION_MAX - which is needed after the reddeer upgrade to 2.0. But we should still fix this. > ITests profile is active by default > ----------------------------------- > > Key: JBIDE-25006 > URL: https://issues.jboss.org/browse/JBIDE-25006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > The intention is that if you run a build of anything depending on the parent pom [1], by default ITests profile is not active. But this doesn't work and it's always active unless you set -DskipITests=true from command line. > The parent pom sets <skipITests>true</skipITests> here: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > And the ITests profile is activated if the skipITests property is not set at all: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > {code} > <activation> > <property> > <name>!skipITests</name> > </property> > </activation> > {code} > We assumed that this would work but it turns out it does not work because profile activation only works with system properties and not properties in a pom. > Pavol suggests simply removing the activation clause for that profile. > [~nickboldt], what do you think of that? It seems simple enough. But who knows if there's hidden consequences to jobs that are used to the current behavior. > Context: Builds of different repos started failing for us. Target platform max contains new RedDeer 2.0 and plugins in master still require RedDeer 1.x which is in target platform min. But it turned out that tpc.version is always set to target platform max which is not expected. So when investigating, we found that once the ITests profile is activated, it will set the tpc.version to max. > This build breakage will disappear once TARGET_PLATFORM_VERSION_MIN is updated to the same version as TARGET_PLATFORM_VERSION_MAX - which is needed after the reddeer upgrade to 2.0. But we should still fix this. > Cc: [~psrna] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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