May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24385) Change www.qa to devstudio.redhat.com on CCI jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24385?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24385: ---------------------------------- Assignee: Rastislav Wagner (was: Nick Boldt) > Change www.qa to devstudio.redhat.com on CCI jobs > ------------------------------------------------- > > Key: JBIDE-24385 > URL: https://issues.jboss.org/browse/JBIDE-24385 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Fix For: 4.4.4.Final, 4.5.0.AM1 > > > Nick can you please change all www.qa downloads to devstudio.redhat.com globally for all jobs on CCI ? thank you -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24385) Change www.qa to devstudio.redhat.com on CCI jobs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24385?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24385: ------------------------------------ Changed applied in https://github.com/jbdevstudio/jbdevstudio-ci/commits/master and pushed to Jenkins. Let me know if I missed any jobs or broke anything. > Change www.qa to devstudio.redhat.com on CCI jobs > ------------------------------------------------- > > Key: JBIDE-24385 > URL: https://issues.jboss.org/browse/JBIDE-24385 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Rastislav Wagner > Assignee: Nick Boldt > > Nick can you please change all www.qa downloads to devstudio.redhat.com globally for all jobs on CCI ? thank you -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24388) merge integration stack content into discovery site CI builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24388?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-24388. -------------------------------- Fix Version/s: (was: 4.5.0.AM1) Resolution: Done Done for 4.4.x. We can enable this in 4.5.x once there's an integration stack site to merge in. > merge integration stack content into discovery site CI builds > ------------------------------------------------------------- > > Key: JBIDE-24388 > URL: https://issues.jboss.org/browse/JBIDE-24388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central-update, integration-platform > Affects Versions: 4.4.4.Final, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > Attachments: IS-in-devstudio-byoe-10.4.0.GA-CI-build-Fuse-and-RHAMT.png > > > Today, we only merge IS content into the discovery site builds during staging and release. > But since this merge operation is now 100% scripted, we could trigger it for all CI builds too. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... for sample of how to run the merge. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24388) merge integration stack content into discovery site CI builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24388?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24388: ------------------------------- Attachment: IS-in-devstudio-byoe-10.4.0.GA-CI-build-Fuse-and-RHAMT.png > merge integration stack content into discovery site CI builds > ------------------------------------------------------------- > > Key: JBIDE-24388 > URL: https://issues.jboss.org/browse/JBIDE-24388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central-update, integration-platform > Affects Versions: 4.4.4.Final, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final, 4.5.0.AM1 > > Attachments: IS-in-devstudio-byoe-10.4.0.GA-CI-build-Fuse-and-RHAMT.png > > > Today, we only merge IS content into the discovery site builds during staging and release. > But since this merge operation is now 100% scripted, we could trigger it for all CI builds too. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... for sample of how to run the merge. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24388) merge integration stack content into discovery site CI builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24388?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24388: ------------------------------------ Done. https://github.com/jbosstools/jbosstools-download.jboss.org/commit/bb55f6... !IS-in-devstudio-byoe-10.4.0.GA-CI-build-Fuse-and-RHAMT.png|thumbnail! > merge integration stack content into discovery site CI builds > ------------------------------------------------------------- > > Key: JBIDE-24388 > URL: https://issues.jboss.org/browse/JBIDE-24388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central-update, integration-platform > Affects Versions: 4.4.4.Final, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final, 4.5.0.AM1 > > Attachments: IS-in-devstudio-byoe-10.4.0.GA-CI-build-Fuse-and-RHAMT.png > > > Today, we only merge IS content into the discovery site builds during staging and release. > But since this merge operation is now 100% scripted, we could trigger it for all CI builds too. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... for sample of how to run the merge. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23963) Create and use Neon.3 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23963?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23963: ------------------------------------ New 4.60.3.Final-SNAPSHOT target platform created and linked from parent pom 4.4.4.Final-SNAPSHOT (new MIN). Updated 4.63.0.Final-SNAPSHOT target platform also linked from parent pom 4.4.4.Final-SNAPSHOT (existing MAX). These were updated to include new Docker Tools 2.3.0.20170425. > Create and use Neon.3 target platform > ------------------------------------- > > Key: JBIDE-23963 > URL: https://issues.jboss.org/browse/JBIDE-23963 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.4.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.4.Final > > Attachments: Screenshot_2017-03-24_11-10-30.png > > > Once available in March, we should move up to Neon.3 > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > devstudio tp, > central tp; > jbt-build-sites (and parent pom), > devstudio site build (and devstudio root pom); > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23317) Create and use Oxygen.0.M7 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23317?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23317: ------------------------------- Summary: Create and use Oxygen.0.M7 target platform (was: Create and use Oxygen.0.M5 (or M7) target platform) > Create and use Oxygen.0.M7 target platform > ------------------------------------------ > > Key: JBIDE-23317 > URL: https://issues.jboss.org/browse/JBIDE-23317 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.0.AM1 > > > Once available on Feb 02/2017, we should create a new 4.70.0.AM1-SNAPSHOT target platform containing Oxygen.0.M5 bits. > https://wiki.eclipse.org/index.php?title=Oxygen/Simultaneous_Release_Plan... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24380) new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME}

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24380?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24380: ------------------------------------ +1 > new default in parent pom: set jbosstools.test.jre.* = ${JAVA_HOME} > ------------------------------------------------------------------- > > Key: JBIDE-24380 > URL: https://issues.jboss.org/browse/JBIDE-24380 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > In order to be able to more easily run server and webservices projects' tests, I suggest we set default values in parent pom: > {code} > - <jbosstools.test.jre.5></jbosstools.test.jre.5> > - <jbosstools.test.jre.6></jbosstools.test.jre.6> > - <jbosstools.test.jre.7></jbosstools.test.jre.7> > - <jbosstools.test.jre.8></jbosstools.test.jre.8> > + <jbosstools.test.jre.5>${JAVA_HOME}</jbosstools.test.jre.5> > + <jbosstools.test.jre.6>${JAVA_HOME}</jbosstools.test.jre.6> > + <jbosstools.test.jre.7>${JAVA_HOME}</jbosstools.test.jre.7> > + <jbosstools.test.jre.8>${JAVA_HOME}</jbosstools.test.jre.8> > {code} > This way, depending on what your system's definition of JAVA_HOME happens to be, you get a different effective pom, for your required JDK: > {code} > $ export JAVA_HOME=/opt/jdk1.8.0/ > $ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre > <jbosstools.test.jre.5>/opt/jdk1.8.0/</jbosstools.test.jre.5> > <jbosstools.test.jre.6>/opt/jdk1.8.0/</jbosstools.test.jre.6> > <jbosstools.test.jre.7>/opt/jdk1.8.0/</jbosstools.test.jre.7> > <jbosstools.test.jre.8>/opt/jdk1.8.0/</jbosstools.test.jre.8> > (or, to use the JAVA_HOME set by alternatives...) > $ export JAVA_HOME=$(alternatives --display java | grep bin/java | grep link | sed -e "s#.\+ $.\+$bin/java#\1#") > $ /opt/maven3/bin/mvn help:effective-pom | grep jbosstools.test.jre > <jbosstools.test.jre.5>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.5> > <jbosstools.test.jre.6>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.6> > <jbosstools.test.jre.7>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.7> > <jbosstools.test.jre.8>/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/</jbosstools.test.jre.8> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1101) Cannot install reddeer feature

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1101?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1101: ----------------------------------- {code} < org.jboss.reddeer.swt [1.2.1.Final] < org.jboss.reddeer.junit [1.2.1.Final] < org.jboss.reddeer.core [1.2.1.Final] < org.jboss.reddeer.common [1.2.1.Final] < org.jboss.reddeer.graphiti.feature.feature.jar [1.2.1.Final] < org.jboss.reddeer.graphiti [1.2.1.Final] < org.jboss.reddeer.graphiti.feature.feature.group [1.2.1.Final] < org.jboss.reddeer.gef [1.2.1.Final] < org.jboss.reddeer.direct [1.2.1.Final] {code} > Cannot install reddeer feature > ------------------------------ > > Key: JBTIS-1101 > URL: https://issues.jboss.org/browse/JBTIS-1101 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.3.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > > The following feature cannot be installed > - org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final > The error is > {code} > Your original request has been modified. > "JBoss Tools Foundation Security for Linux" will be ignored because a newer version is already installed. > Cannot complete the install because one or more required items could not be found. > Software being installed: RedDeer GEF/Graphiti Feature 1.2.1.Final (org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final) > Missing requirement: RedDeer GEF Component 1.2.1.Final (org.jboss.reddeer.gef 1.2.1.Final) requires 'bundle org.jboss.reddeer.workbench [1.2.0,1.3.0)' but it could not be found > Cannot satisfy dependency: > From: RedDeer GEF/Graphiti Feature 1.2.1.Final (org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final) > To: org.jboss.reddeer.gef [1.2.1.Final] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24382) Update Neon.3 target platform using Docker 2.3.0, not 2.3.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24382?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24382: ------------------------------------ TP built. Parent pom updated. Now building the stack: https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > Update Neon.3 target platform using Docker 2.3.0, not 2.3.1 > ----------------------------------------------------------- > > Key: JBIDE-24382 > URL: https://issues.jboss.org/browse/JBIDE-24382 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, target-platform > Affects Versions: 4.4.4.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > Attachments: devstudio-1040GAvsAM3.png, install-devstudio1040ga-ci-snapshot-byoe-docker2.3.0.20170307.png, install-devstudio1040ga-ci-snapshot-byoe.png, p2diff.txt > > > 1. Mirror http://download.eclipse.org/linuxtools/update-docker-neon3respinb to http://download.jboss.org/jbosstools/updates/requirements/docker/2.3.0.20... (Done today.) > 2. Update jbt/ds 4.63.x TPs to use this Neon.3-respin-b version of Docker Tools (PR forthcoming.) > cc: [~jjohnstn] [~lvalach] [~odockal] > Why, you ask? > Well, the 2.3.0.20170425 rebuild of Docker Tools fixes wiring issues w.r.t. docker by depending on OLDER dependencies like spotify.docker 3.4, httpcomponents.httpcore (and httpclient), plus backlevels jnr.* plugins too. > Without this fix [1], installation may pull in an older version of Docker Tools, which depends on newer dependencies. This forces the old deps and the newer feature to be installed and used. > [1] https://github.com/jbosstools/jbosstools-openshift/pull/1492 & https://github.com/jbosstools/jbosstools-openshift/pull/1493 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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