August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26180: ------------------------------------ Coming in the next update, some orbit changes: * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug) > TP: create target platform based on Eclipse 4.9 (Simrel 2018-09) > ---------------------------------------------------------------- > > Key: JBIDE-26180 > URL: https://issues.jboss.org/browse/JBIDE-26180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.9.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final > > Attachments: am1-vs-am2.p2diff.txt > > > In order to start Eclipse 4.9-based builds, we need an updated target platform. > For sprint 152 / AM1: simrel M1 > For sprint 153 / AM2: simrel M2 > For sprint 154 / AM3: simrel M3 > For sprint 155 / GA: simrel RC2/GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-26180 at 8/16/18 6:27 PM: ------------------------------------------------------------- TP rebuilding [0] to pull in newer mylyn 3.24.1 to match the version in nodeclipse site [1]. Hope to fix JBIDE-26065 - p2 director job fails when nodeclipse site and JBT TP have different Mylyn versions. [0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... [1] http://www.nodeclipse.org/updates Also rebuilding to pull in newer m2e-apt (JBIDE-26296). https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... is back to green! was (Author: nickboldt): TP rebuilding [0] to pull in newer mylyn 3.24.1 to match the version in nodeclipse site [1]. Hope to fix JBIDE-26065 - p2 director job fails when nodeclipse site and JBT TP have different Mylyn versions. [0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... [1] http://www.nodeclipse.org/updates Also rebuilding to pull in newer m2e-apt (JBIDE-26296). > TP: create target platform based on Eclipse 4.9 (Simrel 2018-09) > ---------------------------------------------------------------- > > Key: JBIDE-26180 > URL: https://issues.jboss.org/browse/JBIDE-26180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.9.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final > > Attachments: am1-vs-am2.p2diff.txt > > > In order to start Eclipse 4.9-based builds, we need an updated target platform. > For sprint 152 / AM1: simrel M1 > For sprint 153 / AM2: simrel M2 > For sprint 154 / AM3: simrel M3 > For sprint 155 / GA: simrel RC2/GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26305) Jars inside an EAR application are not compressed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26305?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-26305: ------------------------------------- So, let's start by looking here to see when the feature was added: https://github.com/jbosstools/jbosstools-server/blame/58d87019c99ca1b5f9a... This appears to be 3 years ago for the initial feature. So it's not new. It's old. Second, the idea of a config file. In many ways, the server editor itself *is* that config file. So is the "deployment-assembly" preference page. There's no real backing file for the server editor except a hashmap of k/v pairs stored in memory representing the server. There's a config file representing the deployment-assembly in the project named org.eclipse.wst.common.component, but this file doesn't include anything like zipped or unzipped. Third: is there a way to actually customize the zipping behavior of a nested module? Yes, there is, but it's not super intuitive. In the server editor's deployment tab, you can do it. There's the server-level setting as to whether to zip or not zip, but this affects all modules in the server. Below that, you'll see a table listing modules / projects to be deployed. In the case of an ear with a nested jar, you may only see the ear listed here. So you need to use the combo box next to "Filter by: " to "All". This will make the table show all possible modules that can be deployed. When you do this, you can override the settings on a per-module (and even nested module) basis. You can set the ear to unzipped, and the lib jar to zipped. Is this a bug? I don't believe so. There's a way to change settings to properly configure your workspace and server adapter to customize the behavior. The default, I also believe, isn't wrong, because we configure everything for faster incremental deployments. In general, we've been told wildfly and eap have support for exploded nested deployments. If the current configuration breaks their app, the user has two options. First, he should file a bug with wildfly / eap and ask why his scenario doesn't work with exploded deployment and whether it can be fixed. Second, he can customize the deployment behavior as discussed above. I'm open to suggestions here, but for now this is my point of view. > Jars inside an EAR application are not compressed > ------------------------------------------------- > > Key: JBIDE-26305 > URL: https://issues.jboss.org/browse/JBIDE-26305 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Martin Malina > Assignee: Rob Stryker > > A customer has reported an issue where an ear project, when deployed to EAP 7.1, contains exploded jars which then breaks his app. It seems that in his case it happens both in the case of a jar inside a war inside an ear, as well as just a jar inside an ear. > Also, when the customer deploys the same app in the same workspace and same eclipse to EAP 6.4, it works fine - all the jars are zipped. > The customer reports that he can change this behavior in the Deployments tab of the server editor, but it would be nice to be able to define this beforehand in a config file. > I tried to reproduce this in devstudio 12 and in my case the behavior was the same with both EAP 6.4 and 7.1 - in both cases an included jar was exploded which I think is wrong. > So two main things to consider: > 1. Is this a bug? I believe it is - a jar lib should always be zipped by default. Or do you disagree? > 2. Is there a way to specify if a module of an EAP is zipped or not in a config file? If not, can this be added? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26276) Create PR check job for RSP (Runtime Server Protocol)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26276?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-26276: ------------------------------------- [~mmalina] rhdevelopers-ci was added as a collab. I have admin perms. Anything else need to be done here? > Create PR check job for RSP (Runtime Server Protocol) > ----------------------------------------------------- > > Key: JBIDE-26276 > URL: https://issues.jboss.org/browse/JBIDE-26276 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-server-protocol > Reporter: Pavol Srna > Assignee: Martin Malina > Fix For: 4.9.0.AM2 > > > https://github.com/robstryker/org.jboss.tools.ssp/blob/master/Jenkinsfile -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26244) Fuse Tools New and Noteworthy for 4.9.0.AM2

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26244?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-26244: ------------------------------------------- Once someone merges https://github.com/jbosstools/jbosstools-website/pull/846, I'll create a new PR with some additions for the REST tooling... == REST Editor tab improvements The REST tab now provides the ability to add REST Operations to selected Rest Elements in the view, completing the ability to add/edit Rest DSL bits. It is now possible to create a new Rest Configuration, new Rest Elements, and REST Operations on the tab and edit Rest Element and REST Operation properties in the Properties view. > Fuse Tools New and Noteworthy for 4.9.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26244 > URL: https://issues.jboss.org/browse/JBIDE-26244 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Reporter: Jeff MAURY > Assignee: Lars Heinemann > Priority: Critical > Labels: task > Fix For: 4.9.0.AM2 > > > Lars Heinemann, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Fuse Tools JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Fuse Tools, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Fuse Tools by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26236 #comment Create N&N for Fuse Tools 4.9.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Fuse Tools for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26308) ClassNotFoundException due to JBIDE-26164 in CDK/OpenShift tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26308?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-26308 at 8/16/18 10:48 AM: -------------------------------------------------------------- Commit pushed & built [1] after code freeze in effect so this won't be in AM2. Please don't push changes during code freeze. [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... was (Author: nickboldt): Commit pushed after code freeze in effect so this won't be in AM2. Please don't push changes during code freeze. > ClassNotFoundException due to JBIDE-26164 in CDK/OpenShift tooling > ------------------------------------------------------------------ > > Key: JBIDE-26308 > URL: https://issues.jboss.org/browse/JBIDE-26308 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.9.0.AM2 > Reporter: Ondrej Dockal > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: Regression > Fix For: 4.9.0.AM3 > > Attachments: Screenshot_20180816_145542.png > > > There is ClassNotFoundException thrown while working with CDK/Openshift tooling, that is caused by not changed package name for class attribute in plugin.xml that does no correspond with package renaming made in JBIDE-26164. > This was not changed: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or... > I am not sure how about other plugins within openshift repo. [~adietish] dare to take a look and check the rest of them? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26308) ClassNotFoundException due to JBIDE-26164 in CDK/OpenShift tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26308?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26308: ------------------------------------ Commit pushed after code freeze in effect so this won't be in AM2. Please don't push changes during code freeze. > ClassNotFoundException due to JBIDE-26164 in CDK/OpenShift tooling > ------------------------------------------------------------------ > > Key: JBIDE-26308 > URL: https://issues.jboss.org/browse/JBIDE-26308 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.9.0.AM2 > Reporter: Ondrej Dockal > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: Regression > Fix For: 4.9.0.AM3 > > Attachments: Screenshot_20180816_145542.png > > > There is ClassNotFoundException thrown while working with CDK/Openshift tooling, that is caused by not changed package name for class attribute in plugin.xml that does no correspond with package renaming made in JBIDE-26164. > This was not changed: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or... > I am not sure how about other plugins within openshift repo. [~adietish] dare to take a look and check the rest of them? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26308) ClassNotFoundException due to JBIDE-26164 in CDK/OpenShift tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26308?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26308: ------------------------------- Fix Version/s: 4.9.0.AM3 > ClassNotFoundException due to JBIDE-26164 in CDK/OpenShift tooling > ------------------------------------------------------------------ > > Key: JBIDE-26308 > URL: https://issues.jboss.org/browse/JBIDE-26308 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.9.0.AM2 > Reporter: Ondrej Dockal > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: Regression > Fix For: 4.9.0.AM3 > > Attachments: Screenshot_20180816_145542.png > > > There is ClassNotFoundException thrown while working with CDK/Openshift tooling, that is caused by not changed package name for class attribute in plugin.xml that does no correspond with package renaming made in JBIDE-26164. > This was not changed: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or... > I am not sure how about other plugins within openshift repo. [~adietish] dare to take a look and check the rest of them? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26065) [Red Hat Central] Add connector for nodeclipse

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26065?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-26065. ------------------------------ > [Red Hat Central] Add connector for nodeclipse > ---------------------------------------------- > > Key: JBIDE-26065 > URL: https://issues.jboss.org/browse/JBIDE-26065 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, central-update, updatesite, upstream > Affects Versions: 4.6.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.6.0.Final, 4.9.0.AM2 > > Attachments: devstudio12-central.png, eclipse-marketplace-nodeclipse.png, license-node-asl2.txt, license-node-chromium.txt, license-node-jshint-eclipse-license-unknown.txt, license-node-markdown-editor-EPL-version-unknown.txt, license-nodepluginslist-paul-verest.txt, node-license-agreements.png > > > Steps to perform: > -a) mirror a copy of the latest Nodeclipse update site onto dl.jb.org for reproduceability- > -b) add that to the 3rd party target platform used for building RH Central- > c) create a connector in Central for installing Nodeclipse into BOTH *devstudio* and *jbosstools* > (Mirroring step removed because we don't yet have confirmation from Legal that we are permitted to redistribute. So instead we'll just link to upstream remote site.) > The list of features to include will be those recommended in the screenshots here [1], under the *B) UPDATE SITE (BIGGER CHOICE)* section, or can be collected based on the existing Eclipse Marketplace connector provided by nodeclipse [2]. > > [1] http://www.nodeclipse.org/updates/ > [2] https://marketplace.eclipse.org/content/nodeclipse > !eclipse-marketplace-nodeclipse.png|thumbnail! > Installed size is about 111M for these 14 features: > {code} > org.nodeclipse_1.0.2.201509250223 > org.nodeclipse.enide.editors.jade.feature_1.0.2.201509250223 > org.nodeclipse.pluginslist.feature_1.0.2.201509250223 > com.eclipsesource.jshint.feature_0.10.1.20160216-0911 > de.bastiankrol.startexplorer.feature_1.7.0 > gitaddon.feature_1.0.0.20140303-0606 > markdown.editor.feature_1.2.0.201501260515 > net.mihai-nita.ansicon_1.3.1.201508091828 > pm.eclipse.editbox.feature_0.70.0.201508180438 > org.chromium.debug_0.3.9.201509250223 > org.chromium.sdk_0.3.9.201509250223 > tern-feature_1.1.0.201511082254 > tern-jsdt-feature_1.1.0.201511082254 > tern-server-nodejs-feature_1.1.0.201511082254 > {code} > If any of these assumptions / feature brief details are incorrect, please correct them in this description or add comments to this JIRA. > PR to do mirror, if licenses are allowed: > https://github.com/jbosstools/jbosstools-download.jboss.org/pull/638 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26300) Update to latest Tern 1.3 in JST/JSDT

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26300?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-26300 at 8/16/18 10:18 AM: -------------------------------------------------------------- With PR [1], two tests are now failing [2]. [1] https://github.com/jbosstools/jbosstools-jst/pull/593 [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... {code} Failed tests: junit.framework.AssertionFailedError: The proposal Display Strings is/are not found: [Boolean(value) : bool - ecma5][Boolean : fn - ecma5] expected:<0> but was:<2> at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:135) at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma5(JstJsdtTernCATest.java:72) testJstJsdtTernCAOnEcma6(org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest) Time elapsed: 1.868 sec <<< FAILURE! junit.framework.AssertionFailedError: The proposal Display Strings is/are not found: [Array : Array - ecma6][ArrayBuffer(length) - ecma6][ArrayBuffer : fn - ecma6] expected:<0> but was:<3> at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:135) at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma6(JstJsdtTernCATest.java:76) {code} was (Author: nickboldt): With PR [1], two tests are now failing [2]. [1] https://github.com/jbosstools/jbosstools-jst/pull/593 [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Update to latest Tern 1.3 in JST/JSDT > ------------------------------------- > > Key: JBIDE-26300 > URL: https://issues.jboss.org/browse/JBIDE-26300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jst > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Fix For: 4.9.0.AM3 > > > Pull 1.3 from http://oss.opensagres.fr/tern.repository/snapshots/ > Check if we have fewer CVEs after update: > 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, 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 2018