December 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-3570) Include eap-6.4-CVE-2015-7501 into JBDS installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3570?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-3570. ------------------------------ Resolution: Done > Include eap-6.4-CVE-2015-7501 into JBDS installer > ------------------------------------------------- > > Key: JBDS-3570 > URL: https://issues.jboss.org/browse/JBDS-3570 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build > Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Critical > Fix For: 9.1.0.Beta1, 10.0.0.Alpha1 > > > During the whole thing about JBDS-3560, JBDS-3561 and JBDS-3562, Nick changed JBDS 9.1.0 to use the internal build of EAP 6.4.5 in the build process: > 4.3.x branch: > https://github.com/jbdevstudio/jbdevstudio-product/commit/c8aea70202616df... > And in master: > https://github.com/jbdevstudio/jbdevstudio-product/commit/6792edbfefcf54d... > I understand that some of the above mentioned JIRAs are not resolved yet, but I wanted to be sure to track this - we need to make sure not to bundle this build of EAP, because it's an internal build not supposed to be public. (Yes, the original assumption was that perhaps this time there would be an exception, but it turned out not to be the case.) > For JBDS 9.1.0.Beta1 I suggest we include the same patched EAP as discussed in JBDS-3562 . But it's kind of tricky how to make it obvious to users - I'm not sure if we want to include the CVE in the filename again. > But in any case, we can never include EAP 6.4.5 full build. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21190) Should we update wildfly icon / banner?

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21190?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21190: -------------------------------- Fix Version/s: 4.3.1.Beta1 > Should we update wildfly icon / banner? > --------------------------------------- > > Key: JBIDE-21190 > URL: https://issues.jboss.org/browse/JBIDE-21190 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1 > > Attachments: JBIDE-21190.png, JBIDE-21190_v2.png > > > Wildfly is still using the jboss-by-redhat logo. Is this still appropriate? How about for the icon for the server itself? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3571) Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3571?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3571: ------------------------------------ It's probably also worth informing the users/readers that they can verify that they have the correct EAP installed by reviewing the installed patches - as reported by the EAP admin console: !patch.png|thumbnail! > Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501 > ------------------------------------------------------- > > Key: JBDS-3571 > URL: https://issues.jboss.org/browse/JBDS-3571 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation > Affects Versions: 9.0.0.CVE-2015-7501-GA > Reporter: Len DiMaggio > Assignee: Jiri Pallich > Fix For: 9.0.0.CVE-2015-7501-GA > > Attachments: patch.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3571) Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3571?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3571: ------------------------------- Attachment: patch.png > Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501 > ------------------------------------------------------- > > Key: JBDS-3571 > URL: https://issues.jboss.org/browse/JBDS-3571 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation > Affects Versions: 9.0.0.CVE-2015-7501-GA > Reporter: Len DiMaggio > Assignee: Jiri Pallich > Fix For: 9.0.0.CVE-2015-7501-GA > > Attachments: patch.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21145) Composite install job does not reliably install all JBT IUs and so does not see changes between CI builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21145: ------------------------------------ To explain our current process / job interconnections again... * composite site job performs an install to see if anything has changed. If so, it kicks off the aggregate jobs. * when aggregates are done, they check to see if anything has changed (currently this is just a buildinfo.json diff, not a p2diff -- but we can add that in JBDS-16970). If nothing new, no new publish. * then JBDS is built. When done, check to see if anything has changed (currently this is just a buildinfo.json diff, not a p2diff -- but we can add that in JBDS-16970). If nothing new, no new publish. * then discovery sites are built & versionwatch verification is kicked (in parallel, downstream from JBDS build) * Once discovery is refreshed, THEN we do p2 director and install-grinder install tests of JBT and JBDS. Because these tests require a fully-functional JBT, JBDS, Central, and EA site. SO... if you're suggesting that the outcome of a p2diff in the JBT aggregate jobs should control whether or not to fire the install tests, we can certainly do that. But we already prevent running those install tests by preventing upstream from firing downstream. If no new JBT, then no new JBDS, and therefore no new discovery, so no new install tests. Right now the mechanism to determine if/when to fire install tests is "new JBT? new JBDS? new discovery? OK, then new install tests." And that's currently controlled by 2 levels of buildinfo.json SHA diffing - first in JBT, then again in JBDS. So... TL;DR, I think we actually agree here. Scary. > Composite install job does not reliably install all JBT IUs and so does not see changes between CI builds > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21145 > URL: https://issues.jboss.org/browse/JBIDE-21145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Pavol Srna > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > We have often seen old artifacts on nightly sites (mars and neon too). > It seems that the composite-install job [0], [1] is not reliable. So, the downstream JBT aggregate builds [2], [3] are not triggered automatically to pick up all new changes in the upstream JBT component site builds. > [0] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-... > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 6:15 AM NOT PUBLISHED: UNCHANGED") > [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 3:43 AM NOT PUBLISHED: UNCHANGED") > Please investigate. > Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21169) Add openshift.cdk feature into JBT Core update site

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21169?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21169. --------------------------------- I verified that jbdevstudio-9.1.0.Beta1-B163 contains the cdk feature: org.jboss.tools.openshift.cdk.feature_3.1.0.Beta1-v20151205-0342-B106 Since the patch in master is the same, I consider this adequate enough to close this JIRA. > Add openshift.cdk feature into JBT Core update site > --------------------------------------------------- > > Key: JBIDE-21169 > URL: https://issues.jboss.org/browse/JBIDE-21169 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Recently CDK server adapter was added to openshift repo. > JBIDE-20990 > It's a new feature: > org.jboss.tools.openshift.cdk.feature > But this feature is missing from the aggregate update site: > http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars... > It is, however, included in the component update site: > http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-ope... > Max pointed me to JBIDE-21145 but I think it's about something else. Feel free to close this if I'm wrong. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3571) Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3571?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3571: ----------------------------- Target Release: 9.0.0.CVE-2015-7501-GA > Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501 > ------------------------------------------------------- > > Key: JBDS-3571 > URL: https://issues.jboss.org/browse/JBDS-3571 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation > Affects Versions: 9.0.0.CVE-2015-7501-GA > Reporter: Len DiMaggio > Assignee: Jiri Pallich > Fix For: 9.0.0.CVE-2015-7501-GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3571) Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3571?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3571: ------------------------------------- Nick and Alexey and I agreed that we will simply remove the original jbds+eap installer jar (jboss-devstudio-9.0.0.GA-installer-eap.jar) and add the new jar instead (jboss-devstudio-9.0.0.GA-CVE-2015-7501-installer-eap.jar). There are several places where you can get the installer: http://tools.jboss.org/downloads/devstudio/mars/9.0.0.GA.html http://www.jboss.org/products/devstudio/download/ https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?produ... It would be good if each of the places included a link to the document with explanation. There are a couple of existing docs about the CVE (none of them mentions JBDS): https://access.redhat.com/articles/2051353 - internal article https://access.redhat.com/security/cve/CVE-2015-7501 - list of erratas for each product https://access.redhat.com/solutions/2045023 - list of affected products > Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501 > ------------------------------------------------------- > > Key: JBDS-3571 > URL: https://issues.jboss.org/browse/JBDS-3571 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation > Affects Versions: 9.0.0.GA-CVE-2015-7501 > Reporter: Len DiMaggio > Assignee: Jiri Pallich > Fix For: 9.0.0.GA-CVE-2015-7501 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3562) Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3562?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3562: ---------------------------------- Max asked a question: {quote}> > About dialog shows full version with timestamp. > And it won't be different, right ? > We are not shipping actual different eclipse binaries, right ?{quote} Yes, same binaries. Same timestamps everywhere but the installer jar itself and the stuff noted above. {code} $➔ ls jboss-devstudio-9.0.0.GA-v20151206-1918-B12-installer-eap/studio/{features,plugins}/ | grep com.jboss.* com.jboss.devstudio.core.capabilities.feature_9.0.0.GA-v20151002-2235-B124 com.jboss.devstudio.core.feature_9.0.0.GA-v20151002-2235-B124 com.jboss.devstudio.core_9.0.0.GA-v20151002-2235-B124.jar com.jboss.devstudio.core.capabilities_9.0.0.GA-v20151002-2235-B124.jar com.jboss.devstudio.core.central_9.0.0.GA-v20151002-2235-B124.jar com.jboss.devstudio.core.project.examples_9.0.0.GA-v20151002-2235-B124.jar com.jboss.devstudio.core.usage.branding_9.0.0.GA-v20151002-2235-B124.jar {code} > Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 / CVE-2015-7501) > -------------------------------------------------------------------------- > > Key: JBDS-3562 > URL: https://issues.jboss.org/browse/JBDS-3562 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.1.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.1.GA > > Attachments: 900GAvs901GA_B6.p2diff.txt, JBDS900GA-respin_diffs__EAP640-BZ1281963.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640.png, JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640__002.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_210_refs.png, JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_224_refs.png, JBDS900GA-respin_diffs__o.e.jst.plugins.manifest.mf.png, JBDS900GA-respin_diffs__p2director.manifest.mf.png, JBDS900GA-respin_diffs__plugins_including_gson2.1.0vs.2.2.4.png, JBDS900GA-respin_diffs__readme.txt.png > > > Tracker JIRA to house things to do to prepare for 9.0.1 / 9.1.0 branches & builds. > Because JBDS 9.0.0 includes the compromised version of > apache.commons.collections (JBDS-3560, JBDS-3561), we need to at some point respin it, which > will include: > a) updated JBT/JBDS target platforms 4.50.1.* and 4.51.1.* > b) repin of JBDS update sites and installer jars > To that end, I've created the following new branches: > https://github.com/jbosstools/jbosstools-target-platforms/commits/4.50.1.x > https://github.com/jbosstools/jbosstools-target-platforms/commits/4.51.1.x > And I've bumped the version of the target platforms in the 4.50.x and > 4.51.x branches to 4.50.2.Beta1-SNAPSHOT and 4.51.2.Beta1-SNAPSHOT, > respectively. > JBDS is now at version 9.1.0 in the 4.3.x branch and 9.0.1 in the > 4.3.1.x branch. > https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3... > (new, 9.0.1) > https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3.x > (updated to 9.1.0) > So, now we just need to ensure that the correct BUILD_ALIAS (CR1 for > 9.0.1, Beta1 for 9.1.0) and target platforms are used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3571) Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3571?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3571: -------------------------------- Summary: Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501 (was: Release note required for JBDS 9.0.1) > Documentation for JBDS 9.0.0.GA EAP 6.4.0 CVE-2015-7501 > ------------------------------------------------------- > > Key: JBDS-3571 > URL: https://issues.jboss.org/browse/JBDS-3571 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation > Affects Versions: 9.0.1.GA > Reporter: Len DiMaggio > Assignee: Jiri Pallich > Fix For: 9.0.1.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 December 2015