August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22382: ------------------------------------- Will anything be changing here for the eap icon? The linked issue still uses shadowman, which means it doesn't exactly fix up the confusion listed here. > Use different icons for EAP server and Red Hat Central > ------------------------------------------------------ > > Key: JBIDE-22382 > URL: https://issues.jboss.org/browse/JBIDE-22382 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: James Cobb > Priority: Minor > Labels: respin-a > Fix For: 4.4.1.Final > > Attachments: central-rhd-icon.png, fullIDE.png, tools_rebrand.png > > > If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different. -- 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: ------------------------------------ {quote} 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]{quote} The openshift.cdk.feature.source is NOT IN the baseline site (we forgot to add the source feature) so Tycho is removing the source feature from the reactor. And it's using the old version of the "main artifact", openshift.cdk.feature. I wonder if the replacement is happening because we used a SNAPSHOT dependency (openshift-restclient jar) inside the openshift.client plugin (which is in the openshift.feature, which is in the openshift.cdk.feature), so Tycho things the cdk.feature is the same (sources unchanged), but it's not (nested binary has changed). So, yes, we need to bump the feature. PR: https://github.com/jbosstools/jbosstools-openshift/pull/1288 > 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-23021) script checking if all the latest SHAs have been built

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23021?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23021: ------------------------------- Story Points: 3 Sprint: devex #119 August 2016 > script checking if all the latest SHAs have been built > ------------------------------------------------------ > > Key: JBIDE-23021 > URL: https://issues.jboss.org/browse/JBIDE-23021 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Fix For: 4.4.1.Final > > > Need a tool that can compare the latest SHA for a github project on a given branch against a published buildinfo.json. > Should be able to check either jbosstools-base vs. CI build, or jbosstools-base vs. jbt aggregate build's buildinfo.json -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23021) script checking if all the latest SHAs have been built

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23021?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23021: ---------------------------------- Assignee: Nick Boldt > script checking if all the latest SHAs have been built > ------------------------------------------------------ > > Key: JBIDE-23021 > URL: https://issues.jboss.org/browse/JBIDE-23021 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Need a tool that can compare the latest SHA for a github project on a given branch against a published buildinfo.json. > Should be able to check either jbosstools-base vs. CI build, or jbosstools-base vs. jbt aggregate build's buildinfo.json -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23021) script checking if all the latest SHAs have been built

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23021?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23021: ------------------------------- Fix Version/s: 4.4.1.Final > script checking if all the latest SHAs have been built > ------------------------------------------------------ > > Key: JBIDE-23021 > URL: https://issues.jboss.org/browse/JBIDE-23021 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Need a tool that can compare the latest SHA for a github project on a given branch against a published buildinfo.json. > Should be able to check either jbosstools-base vs. CI build, or jbosstools-base vs. jbt aggregate build's buildinfo.json -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23021) script checking if all the latest SHAs have been built

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23021?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23021 at 8/18/16 11:43 AM: -------------------------------------------------------------- Need to expand functionality of https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... so it can be used to diff github vs. json instead of just json vs. json. Once the script is enhanced, can then add that into https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... so it can run more fequently & verify that all commits are done before doing a stage. Could also create a buildflow orchestrator job, so that missing commits can be built and pushed to download.jboss.org. was (Author: nickboldt): Need to expand functionality of https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... so it can be used to diff github vs. json instead of just json vs. json. > script checking if all the latest SHAs have been built > ------------------------------------------------------ > > Key: JBIDE-23021 > URL: https://issues.jboss.org/browse/JBIDE-23021 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > > Need a tool that can compare the latest SHA for a github project on a given branch against a published buildinfo.json. > Should be able to check either jbosstools-base vs. CI build, or jbosstools-base vs. jbt aggregate build's buildinfo.json -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23021) script checking if all the latest SHAs have been built

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23021: ---------------------------------- Summary: script checking if all the latest SHAs have been built Key: JBIDE-23021 URL: https://issues.jboss.org/browse/JBIDE-23021 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: build Affects Versions: 4.4.1.AM3 Reporter: Nick Boldt Need a tool that can compare the latest SHA for a github project on a given branch against a published buildinfo.json. Should be able to check either jbosstools-base vs. CI build, or jbosstools-base vs. jbt aggregate build's buildinfo.json -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23021) script checking if all the latest SHAs have been built

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23021?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23021: ------------------------------------ Need to expand functionality of https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... so it can be used to diff github vs. json instead of just json vs. json. > script checking if all the latest SHAs have been built > ------------------------------------------------------ > > Key: JBIDE-23021 > URL: https://issues.jboss.org/browse/JBIDE-23021 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > > Need a tool that can compare the latest SHA for a github project on a given branch against a published buildinfo.json. > Should be able to check either jbosstools-base vs. CI build, or jbosstools-base vs. jbt aggregate build's buildinfo.json -- 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 commented on JBIDE-23008: ---------------------------------------- Note that from build perspective, bumping the version is the best approach as we're not supposed to produce new artifacts for a version that's already released (=done, immutable, complete, nothing new can happen). > 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 Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23008?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-23008: ---------------------------------------- So the content didn't change, but the build generates a new artifact... At first sight, I would imagine it could be reported as a bug against Tycho. A workaround could be to bump the version of the cdk.server bundle (and similar one who just received source bundles), to avoid this baseline failure. Would that be ok from dev POV ? > 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

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