December 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-3570) Remove EAP 6.4.5 from JBDS installer

by Martin Malina (JIRA)

Martin Malina created JBDS-3570: ----------------------------------- Summary: Remove EAP 6.4.5 from 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 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] (JBDS-3570) Remove EAP 6.4.5 from JBDS installer

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3570?page=com.atlassian.jira.plugin.... ] Martin Malina reassigned JBDS-3570: ----------------------------------- Assignee: Nick Boldt > Remove EAP 6.4.5 from 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 > 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-20938) Report proper error when blog author is unknown

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20938?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-20938: ---------------------------------- Fix Version/s: (was: 4.3.1.Beta1) > Report proper error when blog author is unknown > ----------------------------------------------- > > Key: JBIDE-20938 > URL: https://issues.jboss.org/browse/JBIDE-20938 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: website > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha1 > > > Building the website fails hard if a blog entry has a unknown author. There should be a proper error message instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21179) Upgrade Forge Runtime to 3.0.0.Alpha2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21179?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-21179: ----------------------------------------- Hi Max, these are all valid concerns, thanks for bringing this up: a) The only compatibility it breaks is regarding to executing scripts. The AngularJS cheatsheet wizard does not use scripts, therefore it won't be affected (in fact none of our existing integrations use scripts so far). b) Absolutely. I am targeting the 3.0.0.Final release to February, 15th. The codebase (with the exception of shell command name format) remains compatible. The major upgrade bump was mostly to support JDK 8. Let me know if you have any more questions, if not, feel free to mark this issue as resolved. > Upgrade Forge Runtime to 3.0.0.Alpha2 > ------------------------------------- > > Key: JBIDE-21179 > URL: https://issues.jboss.org/browse/JBIDE-21179 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > -- 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 Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3562?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3562: ------------------------------------- Thanks for the details, Nick. I compared jboss-devstudio-9.0.0.GA-installer-eap.jar and jboss-devstudio-9.0.0.GA-CVE-2015-7501-installer-eap.jar and found this: 1. Different version of Google.gson - I'm fine with your explanation above. 2. Tons of changes in html pages inside org.eclipse.wst.jsdt.doc_1.4.101.v201507140011.jar One example: {code} diff -r 1/reference/api/serialized-form.html 2/reference/api/serialized-form.html 5c5 <  --- >  8c8 < <meta name="date" content="2015-09-08"> --- > <meta name="date" content="2015-09-15"> {code} So it's not exactly the same build of the package, but I'm not really concerned about that. 3. Differences in EAP This one is interesting. Of course there is the .overlay dir with the path. But for some reason the original commons-collections jars have different md5 sum: {code} MD5 (commons/commons-collections-3.2.1.redhat-3.jar) = 2d336af47bc6e8b6b35c930143b3b65c MD5 (commons-cve/commons-collections-3.2.1.redhat-3.jar) = 4e7ee802e16b13d42343cd789c6baaf7 {code} When I extract them both and then compare again using diff, it is exactly the same. I don't know why is that. In the past the patch mechanism would cripple the original jar, but I don't think it does that anymore. Anyway, I'm not worried about this, because the old jar is not used when the patch is applied. I smoke tested the new build and didn't see any problems. > 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__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] (JBIDE-21145) Composite install job does not reliably install all JBT IUs and so does not see changes between CI builds

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21145: --------------------------------------------- The proposal I went for was: JBT aggregate build p2 diff check comparing local JBT aggregate with last published JBT aggregate local JBT aggregate p2 director install test If there is no diff then the install test don't even need to run. It still makes sense to have composite install tests running since not everyting is in sync for aggregateand the composite - but at least for the aggregate "chain of events" much less moving parts are needed and you can skip the install tests in most cases. > 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 commented on JBIDE-21169: --------------------------------------- Cc: [~rob.stryker], [~fbricon] ;) But should be all good now. I can see it here: http://www.qa.jboss.com/binaries/RHDS/9.0/snapshots/builds/devstudio.prod... And here: http://download.jboss.org/jbosstools/neon/snapshots/updates/core/master/ And here: http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/ And when I'm done downloading latest JBDS 9.1.0 I will see if it works there. > 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] (JBIDE-21193) runtime detection detects *any* folder as a CDK and jboss multiple times

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21193?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21193: ---------------------------------------- Attachment: Java_EE_-_jboss-eap-6_1_CDK_Server_-_Eclipse.png > runtime detection detects *any* folder as a CDK and jboss multiple times > ------------------------------------------------------------------------ > > Key: JBIDE-21193 > URL: https://issues.jboss.org/browse/JBIDE-21193 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.3.1.Beta1 > > Attachments: Java_EE_-_jboss-eap-6_1_CDK_Server_-_Eclipse.png > > > with build from last week I now get this list of runtime detected in my folder of servers. > At first I thought it was the CDK being weird but something is also very weird about the basic runtime detection since I seem to have multiple WildFly 8.0's...as opposed to using the folder name. > Here is the content of my folder > {code} > apache-karaf-2.3.5 > apache-tomcat-7.0.35 > app.js > app.js.1 > fsw-6 > jboss as 7 > jboss-5.1.0.GA > jboss-as-7.0.1.Final > jboss-as-7.1.0.Final > jboss-as-7.1.1.Final > jboss-as-web-7.0.0.Final > jboss-as-web-7.0.2.Final > jboss-eap-6.0.1 > jboss-eap-6.1 > weld-1.1.0.Final > weld-1.1.5.Final > wildfly-10.0.0.CR4 > wildfly-8.0.0.Beta1 > wildfly-8.0.0.Final > wildfly-8.1.0.Final > wildfly-8.2.0 > wildfly-core-8.0.0.Final > {code} > and attached is the list I get. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21193) runtime detection detects *any* folder as a CDK and jboss multiple times

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21193?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21193: ---------------------------------------- Fix Version/s: 4.3.1.Beta1 > runtime detection detects *any* folder as a CDK and jboss multiple times > ------------------------------------------------------------------------ > > Key: JBIDE-21193 > URL: https://issues.jboss.org/browse/JBIDE-21193 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.3.1.Beta1 > > Attachments: Java_EE_-_jboss-eap-6_1_CDK_Server_-_Eclipse.png > > > with build from last week I now get this list of runtime detected in my folder of servers. > At first I thought it was the CDK being weird but something is also very weird about the basic runtime detection since I seem to have multiple WildFly 8.0's...as opposed to using the folder name. > Here is the content of my folder > {code} > apache-karaf-2.3.5 > apache-tomcat-7.0.35 > app.js > app.js.1 > fsw-6 > jboss as 7 > jboss-5.1.0.GA > jboss-as-7.0.1.Final > jboss-as-7.1.0.Final > jboss-as-7.1.1.Final > jboss-as-web-7.0.0.Final > jboss-as-web-7.0.2.Final > jboss-eap-6.0.1 > jboss-eap-6.1 > weld-1.1.0.Final > weld-1.1.5.Final > wildfly-10.0.0.CR4 > wildfly-8.0.0.Beta1 > wildfly-8.0.0.Final > wildfly-8.1.0.Final > wildfly-8.2.0 > wildfly-core-8.0.0.Final > {code} > and attached is the list I get. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21193) runtime detection detects *any* folder as a CDK and jboss multiple times

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-21193: ------------------------------------------- Summary: runtime detection detects *any* folder as a CDK and jboss multiple times Key: JBIDE-21193 URL: https://issues.jboss.org/browse/JBIDE-21193 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Reporter: Max Rydahl Andersen Priority: Blocker with build from last week I now get this list of runtime detected in my folder of servers. At first I thought it was the CDK being weird but something is also very weird about the basic runtime detection since I seem to have multiple WildFly 8.0's...as opposed to using the folder name. Here is the content of my folder {code} apache-karaf-2.3.5 apache-tomcat-7.0.35 app.js app.js.1 fsw-6 jboss as 7 jboss-5.1.0.GA jboss-as-7.0.1.Final jboss-as-7.1.0.Final jboss-as-7.1.1.Final jboss-as-web-7.0.0.Final jboss-as-web-7.0.2.Final jboss-eap-6.0.1 jboss-eap-6.1 weld-1.1.0.Final weld-1.1.5.Final wildfly-10.0.0.CR4 wildfly-8.0.0.Beta1 wildfly-8.0.0.Final wildfly-8.1.0.Final wildfly-8.2.0 wildfly-core-8.0.0.Final {code} and attached is the list I get. -- 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