September 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-26302) Reduce CVE issues in JBT seam bundles

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26302?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26302: ------------------------------------ Ping on this issue -- will this get done for GA? > Reduce CVE issues in JBT seam bundles > ------------------------------------- > > Key: JBIDE-26302 > URL: https://issues.jboss.org/browse/JBIDE-26302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.9.0.Final > > > Some CVE issues exist in seam bundles: > {code} > org.jboss.tools.cdi.seam.core_1.8.301.v20180807-1920.jar > org.jboss.tools.maven.seam_1.9.1.v20180802-1520.jar{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Verification: check if we have fewer CVEs after updating to newer version of fuse 11.1.x: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. #103 > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. build #87 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26283: ------------------------------------ Issue did not reoccur after moving to 4.9.0.Final - https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is green. So, resolving. > Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26283 > URL: https://issues.jboss.org/browse/JBIDE-26283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.9.0.Final > > Attachments: diff-baseline-with-local-build-commented-timestamps.png, diff-baseline-with-local-build-sourcereferences-cause-problem.png > > > Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is red for one week. > More info: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-26283. -------------------------------- Resolution: Cannot Reproduce > Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26283 > URL: https://issues.jboss.org/browse/JBIDE-26283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.9.0.Final > > Attachments: diff-baseline-with-local-build-commented-timestamps.png, diff-baseline-with-local-build-sourcereferences-cause-problem.png > > > Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is red for one week. > More info: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26302) Reduce CVE issues in JBT seam bundles

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26302?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26302: ---------------------------------- Assignee: Jeff MAURY (was: Nick Boldt) > Reduce CVE issues in JBT seam bundles > ------------------------------------- > > Key: JBIDE-26302 > URL: https://issues.jboss.org/browse/JBIDE-26302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.9.0.Final > > > Some CVE issues exist in seam bundles: > {code} > org.jboss.tools.cdi.seam.core_1.8.301.v20180807-1920.jar > org.jboss.tools.maven.seam_1.9.1.v20180802-1520.jar{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Verification: check if we have fewer CVEs after updating to newer version of fuse 11.1.x: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. #103 > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. build #87 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4730: -------------------------------- Assignee: James Cobb > [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4730 > URL: https://issues.jboss.org/browse/JBDS-4730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.9.0.AM3 > Reporter: Nick Boldt > Assignee: James Cobb > Priority: Blocker > Fix For: 12.10.0.AM1 > > > Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "Red Hat CodeReady Studio". > As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ > We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-671) [GTK3] Replace deprecated GdkScreen monitor functions with GdkDisplay ones [EBZ#539392]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-671: --------------------------------------- Summary: [GTK3] Replace deprecated GdkScreen monitor functions with GdkDisplay ones [EBZ#539392] Key: ERT-671 URL: https://issues.jboss.org/browse/ERT-671 Project: Eclipse Release Train Issue Type: Task Components: Platform Reporter: Friendly Jira Robot This function is currently dynamic, but still runs on GTK3.22. It should be guarded and used only on GTK3.20-. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26377) Upgrade jacoco jenkins plugin to 0.8.2+

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26377?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26377: ------------------------------------ Jacoco Jenkins plugin 2.2.1 is installed on dev-platform Jenkins. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/pluginManage... {code} About Jenkins JaCoCo plugin 2.2.1 3rd Party Dependencies Name Maven ID License Jenkins JaCoCo plugin org.jenkins-ci.plugins:jacoco:2.2.1 MIT license JaCoCo :: Maven Plugin org.jacoco:jacoco-maven-plugin:0.7.8 Eclipse Public License v1.0 JaCoCo :: Agent org.jacoco:org.jacoco.agent:0.7.8 Eclipse Public License v1.0 Maven Artifact Manager org.apache.maven:maven-artifact-manager:2.2.1 The Apache Software License, Version 2.0 Maven File Management API org.apache.maven.shared:file-management:1.2.1 The Apache Software License, Version 2.0 ASM Tree org.ow2.asm:asm-tree:5.0.1 BSD Maven Project Builder org.apache.maven:maven-project:2.2.1 The Apache Software License, Version 2.0 XML Commons External Components XML APIs xml-apis:xml-apis:1.4.01 The Apache Software License, Version 2.0 The SAX License The W3C License Plexus :: Component Annotations org.codehaus.plexus:plexus-component-annotations:1.5.5 The Apache Software License, Version 2.0 JaCoCo :: Report org.jacoco:org.jacoco.report:0.7.8 Eclipse Public License v1.0 Hamcrest Core org.hamcrest:hamcrest-core:1.3 New BSD License Plexus Common Utilities org.codehaus.plexus:plexus-utils:3.0.24 Apache License, Version 2.0 ASM Core org.ow2.asm:asm:5.0.1 BSD Maven Reporting Implementation org.apache.maven.reporting:maven-reporting-impl:2.1 The Apache Software License, Version 2.0 Default Plexus Container org.codehaus.plexus:plexus-container-default:1.0-alpha-9-stable-1 JaCoCo :: Core org.jacoco:org.jacoco.core:0.7.8 Eclipse Public License v1.0 classworlds classworlds:classworlds:1.1-alpha-2 ASM Commons org.ow2.asm:asm-commons:5.0.1 BSD Maven Repository Metadata Model org.apache.maven:maven-repository-metadata:2.2.1 The Apache Software License, Version 2.0 Apache HttpCore org.apache.httpcomponents:httpcore:4.4.1 Apache License, Version 2.0 asm5 org.kohsuke:asm5:5.0.1 BSD License Maven Profile Model org.apache.maven:maven-profile:2.2.1 The Apache Software License, Version 2.0 Maven Reporting API org.apache.maven.reporting:maven-reporting-api:2.2.1 The Apache Software License, Version 2.0 Maven Shared I/O API org.apache.maven.shared:maven-shared-io:1.1 The Apache Software License, Version 2.0 JUnit junit:junit:4.12 Eclipse Public License 1.0 ASM Debug All org.ow2.asm:asm-debug-all:5.1 BSD Validator commons-validator:commons-validator:1.2.0 The Apache Software License, Version 2.0 Maven Plugin Registry Model org.apache.maven:maven-plugin-registry:2.2.1 The Apache Software License, Version 2.0 Backport of JSR 166 backport-util-concurrent:backport-util-concurrent:3.1 Public Domain{code} Is that new enough, or are you saying we need newer versions of some different plugins, like: * org.jacoco:jacoco-maven-plugin:0.7.8 * org.jacoco:org.jacoco.agent:0.7.8 * org.jacoco:org.jacoco.report:0.7.8 * org.jacoco:org.jacoco.core:0.7.8 If so, we might need a new release of Jenkins JaCoCo plugin >2.2.1 to include these newer 3rd party libs. cc: [~psrna] [~jrichter1] > Upgrade jacoco jenkins plugin to 0.8.2+ > --------------------------------------- > > Key: JBIDE-26377 > URL: https://issues.jboss.org/browse/JBIDE-26377 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Aurélien Pupier > > requires upgrade of Jenkins plugins > it will allow to benefits from latest fix and improvements of Jacoco and avoids to have to set a specific version of jacoco for each jdk version profile -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26377) Upgrade jacoco jenkins plugin to 0.8.2+

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26377?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26377: ------------------------------- Summary: Upgrade jacoco jenkins plugin to 0.8.2+ (was: Upgrade jacoco to 0.8.2+) > Upgrade jacoco jenkins plugin to 0.8.2+ > --------------------------------------- > > Key: JBIDE-26377 > URL: https://issues.jboss.org/browse/JBIDE-26377 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Aurélien Pupier > > requires upgrade of Jenkins plugins > it will allow to benefits from latest fix and improvements of Jacoco and avoids to have to set a specific version of jacoco for each jdk version profile -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26379) Launcher: should be moved from base to central

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26379?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26379: ------------------------------------------ both patches merged. launcher was moved from jbosstools-base to jbosstools-central. Resolving. > Launcher: should be moved from base to central > ---------------------------------------------- > > Key: JBIDE-26379 > URL: https://issues.jboss.org/browse/JBIDE-26379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, common > Affects Versions: 4.9.0.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: launcher_wizard > Fix For: 4.9.0.Final > > > as discussed in https://github.com/jbosstools/jbosstools-base/pull/631#issuecomment-42109... > {quote} > This should all live in central, and it shouldn't really be added to the common.all feature if we intend to simply move it later. > Give it it's own feature, add it to the master list of features added to the project, and then later move it to the central repo. > I personally believe a rename-and-move is just fine even before a Final. Keeping it where it is through a final actually is what's harder to change. Then it becomes a sort of API that the common.all feature contains this launcher, and later it won't. > {quote} > we should move the launcher from jbosstools-base to jbosstools-central -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26379) Launcher: should be moved from base to central

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26379?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26379: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-central/pull/441, https://github.com/jbosstools/jbosstools-base/pull/632 (was: https://github.com/jbosstools/jbosstools-central/pull/441) > Launcher: should be moved from base to central > ---------------------------------------------- > > Key: JBIDE-26379 > URL: https://issues.jboss.org/browse/JBIDE-26379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, common > Affects Versions: 4.9.0.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: launcher_wizard > Fix For: 4.9.0.Final > > > as discussed in https://github.com/jbosstools/jbosstools-base/pull/631#issuecomment-42109... > {quote} > This should all live in central, and it shouldn't really be added to the common.all feature if we intend to simply move it later. > Give it it's own feature, add it to the master list of features added to the project, and then later move it to the central repo. > I personally believe a rename-and-move is just fine even before a Final. Keeping it where it is through a final actually is what's harder to change. Then it becomes a sort of API that the common.all feature contains this launcher, and later it won't. > {quote} > we should move the launcher from jbosstools-base to jbosstools-central -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 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 2018