June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-320) Node.js plugin should not depend on chromium bundles [EBZ#491528]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-320: --------------------------------------- Summary: Node.js plugin should not depend on chromium bundles [EBZ#491528] Key: ERT-320 URL: https://issues.jboss.org/browse/ERT-320 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot For now org.eclipse.wst.jsdt.js.node bundle depends on org.eclipse.wst.jsdt.chromium.debug.core. This dependency should be quite easily removed due to the fact that only launch parameters from Chromium are used in order to trigger Chromium V8 debug -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-320) Node.js plugin should not depend on chromium bundles [EBZ#491528]

by Friendly Jira Robot (JIRA)

[ https://issues.jboss.org/browse/ERT-320?page=com.atlassian.jira.plugin.sy... ] Friendly Jira Robot resolved ERT-320. ------------------------------------- Resolution: Done > Node.js plugin should not depend on chromium bundles [EBZ#491528] > ----------------------------------------------------------------- > > Key: ERT-320 > URL: https://issues.jboss.org/browse/ERT-320 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: Debug, bzira > > For now org.eclipse.wst.jsdt.js.node bundle depends on org.eclipse.wst.jsdt.chromium.debug.core. This dependency should be quite easily removed due to the fact that only launch parameters from Chromium are used in order to trigger Chromium V8 debug -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-321) JavaScript as-you-type validation shouldn't appear for non-jJSDT projects [EBZ#491637]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-321: --------------------------------------- Summary: JavaScript as-you-type validation shouldn't appear for non-jJSDT projects [EBZ#491637] Key: ERT-321 URL: https://issues.jboss.org/browse/ERT-321 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot JavaScript as-you-type validation works even if a project doesn't have a JSDT nature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-319) NewXMLGenerator NPE [EBZ#459013]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-319: --------------------------------------- Summary: NewXMLGenerator NPE [EBZ#459013] Key: ERT-319 URL: https://issues.jboss.org/browse/ERT-319 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Friendly Jira Robot Fix For: Neon (4.6) M7 We use some WTP internal classes in our unit tests. We are experiencing an NPE in wst.xml code: The offending method reads as follows, with my own comments inline: public void createNamespaceInfoList() { List result = new Vector(); if (cmDocument != null) { // result is set to null here result = (List) cmDocument.getProperty("http://org.eclipse.wst/cm/properties/completeNamespaceInfo"); //$NON-NLS-1$ if (result != null) { // cut out for brevity } NamespaceInfoContentBuilder builder = new NamespaceInfoContentBuilder(); builder.setBuildPolicy(ContentBuilder.BUILD_ONLY_REQUIRED_CONTENT); builder.visitCMNode(cmDocument); result.addAll(builder.list); // NPE HERE } namespaceInfoList = result; } result is initialized as a new Vector(); It then gets set to null when performing cmDocument.getProperty(etc). Later, an attempt to result.addAll(etc) fails because result is null. A possible rewriting of this code would be: public void createNamespaceInfoList() { List result = new Vector(); if (cmDocument != null) { List result2 = (List) cmDocument.getProperty("http://org.eclipse.wst/cm/properties/completeNamespaceInfo"); //$NON-NLS-1$ if (result2 != null) { result = result2; // cut out for brevity } NamespaceInfoContentBuilder builder = new NamespaceInfoContentBuilder(); builder.setBuildPolicy(ContentBuilder.BUILD_ONLY_REQUIRED_CONTENT); builder.visitCMNode(cmDocument); result.addAll(builder.list); // NPE HERE } namespaceInfoList = result; } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-319) NewXMLGenerator NPE [EBZ#459013]

by Friendly Jira Robot (JIRA)

[ https://issues.jboss.org/browse/ERT-319?page=com.atlassian.jira.plugin.sy... ] Friendly Jira Robot resolved ERT-319. ------------------------------------- Resolution: Done > NewXMLGenerator NPE [EBZ#459013] > -------------------------------- > > Key: ERT-319 > URL: https://issues.jboss.org/browse/ERT-319 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: 3.8_M7, bzira, wst.xml > Fix For: Neon (4.6) M7 > > > We use some WTP internal classes in our unit tests. We are experiencing an NPE in wst.xml code: > The offending method reads as follows, with my own comments inline: > public void createNamespaceInfoList() { > List result = new Vector(); > if (cmDocument != null) { > // result is set to null here > result = (List) cmDocument.getProperty("http://org.eclipse.wst/cm/properties/completeNamespaceInfo"); //$NON-NLS-1$ > if (result != null) { > // cut out for brevity > } > NamespaceInfoContentBuilder builder = new NamespaceInfoContentBuilder(); > builder.setBuildPolicy(ContentBuilder.BUILD_ONLY_REQUIRED_CONTENT); > builder.visitCMNode(cmDocument); > result.addAll(builder.list); // NPE HERE > } > namespaceInfoList = result; > } > result is initialized as a new Vector(); It then gets set to null when performing cmDocument.getProperty(etc). Later, an attempt to result.addAll(etc) fails because result is null. > A possible rewriting of this code would be: > public void createNamespaceInfoList() { > List result = new Vector(); > if (cmDocument != null) { > List result2 = (List) cmDocument.getProperty("http://org.eclipse.wst/cm/properties/completeNamespaceInfo"); //$NON-NLS-1$ > if (result2 != null) { > result = result2; > // cut out for brevity > } > NamespaceInfoContentBuilder builder = new NamespaceInfoContentBuilder(); > builder.setBuildPolicy(ContentBuilder.BUILD_ONLY_REQUIRED_CONTENT); > builder.visitCMNode(cmDocument); > result.addAll(builder.list); // NPE HERE > } > namespaceInfoList = result; > } -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-314) Add default entry for 'Docker Hub' in the registry accounts [EBZ#496177]

by Nick Boldt (JIRA)

Nick Boldt created ERT-314: ------------------------------ Summary: Add default entry for 'Docker Hub' in the registry accounts [EBZ#496177] Key: ERT-314 URL: https://issues.jboss.org/browse/ERT-314 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Nick Boldt The registry will just contain the Server Address, so the user will have just to edit the settings to specify the credentials if he/she wants to push images. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-315) Changes in config.xml are not correctly propagated to project [EBZ#496329]

by Nick Boldt (JIRA)

Nick Boldt created ERT-315: ------------------------------ Summary: Changes in config.xml are not correctly propagated to project [EBZ#496329] Key: ERT-315 URL: https://issues.jboss.org/browse/ERT-315 Project: Eclipse Release Train Issue Type: Task Components: Thym Reporter: Nick Boldt Priority: Minor Fix For: Neon (4.6) Thym relies on config.xml for information about the current Cordova project. While changes to config.xml made through Thym functionality correctly update the project and config.xml, changes made directly to config.xml cause the actual project and WidgetModel to be inconsistent. Example: Deleting a plugin tag from config.xml makes it appear as though that plugin was removed from the project, even though the folders for that plugin are still attached to the project, and running `cordova plugin list` from the commandline will list that plugin as still installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-316) Plugin folder decorators do not appear on Linux. [EBZ#496330]

by Nick Boldt (JIRA)

Nick Boldt created ERT-316: ------------------------------ Summary: Plugin folder decorators do not appear on Linux. [EBZ#496330] Key: ERT-316 URL: https://issues.jboss.org/browse/ERT-316 Project: Eclipse Release Train Issue Type: Task Components: Thym Reporter: Nick Boldt Priority: Trivial Fix For: Neon (4.6) Decorators on plugin folders in the plugins subdirectory do not appear when running on Linux (Fedora 23). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-318) Add privileged support to ContainerLauncher class launch method [EBZ#496515]

by Nick Boldt (JIRA)

Nick Boldt created ERT-318: ------------------------------ Summary: Add privileged support to ContainerLauncher class launch method [EBZ#496515] Key: ERT-318 URL: https://issues.jboss.org/browse/ERT-318 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Nick Boldt Fix For: Neon.1 (4.6) Support for the privileged flag is not possible with the current ContainerLauncher.launch method. A change was posted, but it was too late for the major 5.0.0 release. It will be modified for 5.1.0 to simply add API rather than remove or change API. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-317) Run Image Launch Configuration doesn't preserve command quotes [EBZ#496333]

by Nick Boldt (JIRA)

Nick Boldt created ERT-317: ------------------------------ Summary: Run Image Launch Configuration doesn't preserve command quotes [EBZ#496333] Key: ERT-317 URL: https://issues.jboss.org/browse/ERT-317 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Nick Boldt Fix For: Neon.1 (4.6) The string used for the CMD for a Run Image configuration changes each time it is opened. The first time it strips off one set of quotes, the second time it strips off the next, etc.. The CMD string should appear the same each time the configuration is opened. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 June 2016