August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23024) [p2diff] Add ability to do binary comparison of IUs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23024?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23024: ------------------------------- Fix Version/s: 4.4.x > [p2diff] Add ability to do binary comparison of IUs > --------------------------------------------------- > > Key: JBIDE-23024 > URL: https://issues.jboss.org/browse/JBIDE-23024 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Fix For: 4.4.x > > > See https://github.com/irbull/p2diff/issues/12 and JBIDE-22968 for context & why this enhancement is a good one. > Currently, only openshift has the potential to include a nested SNAPSHOT jar in the lib/ folder of openshift.client, so the problem is relatively localized. > In future however this may come back and be more urgent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22968) if a build fails to publish, future builds may think there's nothing new and also not publish

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22968?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-22968. -------------------------------- Resolution: Done Marking resolved. I've opened JBIDE-23024 to track future enhancement in p2diff. > if a build fails to publish, future builds may think there's nothing new and also not publish > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22968 > URL: https://issues.jboss.org/browse/JBIDE-22968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > Attachments: openshift-failed-future-builds-did-not-publish.png > > > When publishing snapshots to download.jboss.org via Jenkins jobs, we need to add a check for "did the last build fail? if so, set skipRevisionCheckWhenPublishing = true" > That way we don't get situations where the Openshift build fails (because failed enforcer check) and then the next 4-5 builds are NOT published (because as far as the current tests are concerned, the latest SHA in Jenkins == latest SHA in github... but NOT the latest SHA on download.jboss.org/.../snapshots/JOB_NAME/latest/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23024) [p2diff] Add ability to do binary comparison of IUs

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23024: ---------------------------------- Summary: [p2diff] Add ability to do binary comparison of IUs Key: JBIDE-23024 URL: https://issues.jboss.org/browse/JBIDE-23024 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: build, upstream Affects Versions: 4.4.1.AM3 Reporter: Nick Boldt See https://github.com/irbull/p2diff/issues/12 and JBIDE-22968 for context & why this enhancement is a good one. Currently, only openshift has the potential to include a nested SNAPSHOT jar in the lib/ folder of openshift.client, so the problem is relatively localized. In future however this may come back and be more urgent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23008) openshift.cdk.feature.source missing from JBT site; causes baseline check to fail

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23008?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-23008 at 8/19/16 10:10 AM: ------------------------------------------------------------------ {quote}no need to have features INCLUDE each other when they're co-published to the same update sites.{quote} The rule is to use include IFF the features are always built and published together. was (Author: nickboldt): [~adietish] Yes, that's part of it. Really, the fix was "touch these 3 files so their jgit timestamp is newer", but that change was also a good one... no need to have features INCLUDE each other when they're co-published to the same update sites. Meanwhile, I've also merged https://github.com/jbosstools/jbosstools-build-sites/pull/247 and https://github.com/jbdevstudio/jbdevstudio-product/pull/395 so that the missing source feature appears on future JBT/ds update sites. > openshift.cdk.feature.source missing from JBT site; causes baseline check to fail > --------------------------------------------------------------------------------- > > Key: JBIDE-23008 > URL: https://issues.jboss.org/browse/JBIDE-23008 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift, updatesite > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Since the weekend (after I published an AM3 build into /neon/staging/updates/): > {code} > [INFO] --- tycho-source-plugin:0.25.0:plugin-source (plugin-source) @ org.jboss.tools.openshift.cdk.server --- > [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT-sources.jar > [INFO] > [INFO] --- target-platform-configuration:0.25.0:target-platform (default-target-platform) @ org.jboss.tools.openshift.cdk.server --- > [INFO] > [INFO] --- tycho-packaging-plugin:0.25.0:package-plugin (default-package-plugin) @ org.jboss.tools.openshift.cdk.server --- > [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT.jar > [INFO] > [INFO] --- tycho-p2-plugin:0.25.0:p2-metadata-default (default-p2-metadata-default) @ org.jboss.tools.openshift.cdk.server --- > [WARNING] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml: baseline and build artifacts have same version but different contents > [INFO] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml > The main artifact has been replaced with the baseline version. > The following attached artifacts are not present in the baseline and have been removed: [sources]{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23008) openshift.cdk.feature.source missing from JBT site; causes baseline check to fail

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23008?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23008: ------------------------------------ [~adietish] Yes, that's part of it. Really, the fix was "touch these 3 files so their jgit timestamp is newer", but that change was also a good one... no need to have features INCLUDE each other when they're co-published to the same update sites. Meanwhile, I've also merged https://github.com/jbosstools/jbosstools-build-sites/pull/247 and https://github.com/jbdevstudio/jbdevstudio-product/pull/395 so that the missing source feature appears on future JBT/ds update sites. > openshift.cdk.feature.source missing from JBT site; causes baseline check to fail > --------------------------------------------------------------------------------- > > Key: JBIDE-23008 > URL: https://issues.jboss.org/browse/JBIDE-23008 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift, updatesite > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Since the weekend (after I published an AM3 build into /neon/staging/updates/): > {code} > [INFO] --- tycho-source-plugin:0.25.0:plugin-source (plugin-source) @ org.jboss.tools.openshift.cdk.server --- > [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT-sources.jar > [INFO] > [INFO] --- target-platform-configuration:0.25.0:target-platform (default-target-platform) @ org.jboss.tools.openshift.cdk.server --- > [INFO] > [INFO] --- tycho-packaging-plugin:0.25.0:package-plugin (default-package-plugin) @ org.jboss.tools.openshift.cdk.server --- > [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT.jar > [INFO] > [INFO] --- tycho-p2-plugin:0.25.0:p2-metadata-default (default-p2-metadata-default) @ org.jboss.tools.openshift.cdk.server --- > [WARNING] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml: baseline and build artifacts have same version but different contents > [INFO] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml > The main artifact has been replaced with the baseline version. > The following attached artifacts are not present in the baseline and have been removed: [sources]{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-334) Add a Docker Image Hierarchy view [EBZ#496308]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-334?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon resolved ERT-334. ------------------------------- Resolution: Done > Add a Docker Image Hierarchy view [EBZ#496308] > ---------------------------------------------- > > Key: ERT-334 > URL: https://issues.jboss.org/browse/ERT-334 > Project: Eclipse Release Train > Issue Type: Feature Request > Components: Linux Tools > Affects Versions: Neon (4.6) > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Neon.1 (4.6) > > > This view could work in more or less the same way as the JDT "Type Hierarchy" view does, but here it would let the user navigate in the hierarchy of layers of a given image. > See https://github.com/justone/dockviz/ for some CLI equivalent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-334) Add a Docker Image Hierarchy view [EBZ#496308]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-334?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-334: ------------------------------ Fix Version/s: Neon (4.6) RC1 (was: Neon.1 (4.6)) > Add a Docker Image Hierarchy view [EBZ#496308] > ---------------------------------------------- > > Key: ERT-334 > URL: https://issues.jboss.org/browse/ERT-334 > Project: Eclipse Release Train > Issue Type: Feature Request > Components: Linux Tools > Affects Versions: Neon (4.6) > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Neon (4.6) RC1 > > > This view could work in more or less the same way as the JDT "Type Hierarchy" view does, but here it would let the user navigate in the hierarchy of layers of a given image. > See https://github.com/justone/dockviz/ for some CLI equivalent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22884) test failure in org.jboss.tools.vpe.jsp.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22884?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22884 at 8/19/16 9:27 AM: ------------------------------------------------------------- Escalating to Blocker since we need all tests working for Final. And this continues to fail in Jenkins. [^22884.more.fail.txt] - from http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... was (Author: nickboldt): Escalating to Blocker since we need all tests working for Final. And this continues to fail in Jenkins. [^22884.more.fail.txt] > test failure in org.jboss.tools.vpe.jsp.test > -------------------------------------------- > > Key: JBIDE-22884 > URL: https://issues.jboss.org/browse/JBIDE-22884 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, visual-page-editor-core > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.4.1.Final > > Attachments: 22884.more.fail.txt, _view_.txt, _view_more.txt > > > {code} > 21:32:03 [INFO] org.jboss.tools.vpe.jsp.test ....................... FAILURE [ 01:00 h] > 21:32:04 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.25.0:test (default-test) on project org.jboss.tools.vpe.jsp.test: An unexpected error occured while launching the test runtime (return code 143). See log for details. -> [Help 1] > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_master... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22884) test failure in org.jboss.tools.vpe.jsp.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22884?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22884 at 8/19/16 9:25 AM: ------------------------------------------------------------- Escalating to Blocker since we need all tests working for Final. And this continues to fail in Jenkins. [^22884.more.fail.txt] was (Author: nickboldt): Escalating to Blocker since we need all tests working for Final. And this continues to fail in Jenkins. > test failure in org.jboss.tools.vpe.jsp.test > -------------------------------------------- > > Key: JBIDE-22884 > URL: https://issues.jboss.org/browse/JBIDE-22884 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, visual-page-editor-core > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.4.1.Final > > Attachments: 22884.more.fail.txt, _view_.txt, _view_more.txt > > > {code} > 21:32:03 [INFO] org.jboss.tools.vpe.jsp.test ....................... FAILURE [ 01:00 h] > 21:32:04 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.25.0:test (default-test) on project org.jboss.tools.vpe.jsp.test: An unexpected error occured while launching the test runtime (return code 143). See log for details. -> [Help 1] > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_master... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22884) test failure in org.jboss.tools.vpe.jsp.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22884?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22884: ------------------------------- Attachment: 22884.more.fail.txt > test failure in org.jboss.tools.vpe.jsp.test > -------------------------------------------- > > Key: JBIDE-22884 > URL: https://issues.jboss.org/browse/JBIDE-22884 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, visual-page-editor-core > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.4.1.Final > > Attachments: 22884.more.fail.txt, _view_.txt, _view_more.txt > > > {code} > 21:32:03 [INFO] org.jboss.tools.vpe.jsp.test ....................... FAILURE [ 01:00 h] > 21:32:04 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.25.0:test (default-test) on project org.jboss.tools.vpe.jsp.test: An unexpected error occured while launching the test runtime (return code 143). See log for details. -> [Help 1] > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_master... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 August 2016