August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-364) Need to automate source lookup detection for front-end debugging [EBZ#497855]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-364?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-364: ------------------------------- Assignee: Ilya Buziuk > Need to automate source lookup detection for front-end debugging [EBZ#497855] > ----------------------------------------------------------------------------- > > Key: ERT-364 > URL: https://issues.jboss.org/browse/ERT-364 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Labels: General, bzira > > For now source lookup for front-end debugging via Web Inspector Protocol (WIP) can be only manually set. Need to implement automatic source lookup detection that will support both file & http protocols. This will allow to debug javascript from JSDT editor OOTB -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22610) generate email notifications when automatically fetching TP mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22610?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22610: ------------------------------------ > How often do we send such emails? Every time we update the TP in a significant way; perhaps 1-3x per sprint. > How much time does it take? 10 minutes? Not sure -- you've sent them too. > Is there usually some small tweaks necessary (that cannot be automated)? Yes, the content changes each time but the changes are all parameterizable, like I have done here [1]. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-push-to-s... (ref: JBIDE-22819) > How much time would it take to automate such notifications? Unknown. > generate email notifications when automatically fetching TP mirrors > ------------------------------------------------------------------- > > Key: JBIDE-22610 > URL: https://issues.jboss.org/browse/JBIDE-22610 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.x > > > TODO: generate email notifications including links to... > * jenkins job, > * diff files, and > * associated JIRA(s), plus > * instructions for how to build the TP locally. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-834) JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-834: -------------------------------- Summary: JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY Key: JBTIS-834 URL: https://issues.jboss.org/browse/JBTIS-834 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: target-platform Affects Versions: 4.3.2.Final-TP Reporter: Paul Leacu Assignee: Paul Leacu Need to add: org.eclipse.swtbot.ide_2.3.0.201506081302.jar as an IS dependency for Fuse/SY from The JBT core TP dependencies are: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... The Mars swtbot JBT mirror is: http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.3.0/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22610) generate email notifications when automatically fetching TP mirrors

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22610?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22610: ---------------------------------------- Ok, thanks for the example. How often do we send such emails? How much time does it take? Is there usually some small tweaks necessary (that cannot be automated)? How much time would it take to automate such notifications? I'm not sure there is an opportunity to save much time nor to improve processes and quality overall here. > generate email notifications when automatically fetching TP mirrors > ------------------------------------------------------------------- > > Key: JBIDE-22610 > URL: https://issues.jboss.org/browse/JBIDE-22610 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.x > > > TODO: generate email notifications including links to... > * jenkins job, > * diff files, and > * associated JIRA(s), plus > * instructions for how to build the TP locally. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22610) generate email notifications when automatically fetching TP mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22610?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22610: ------------------------------------ I'm talking about the notification emails like this one: http://lists.jboss.org/pipermail/jbosstools-dev/2016-May/011296.html > generate email notifications when automatically fetching TP mirrors > ------------------------------------------------------------------- > > Key: JBIDE-22610 > URL: https://issues.jboss.org/browse/JBIDE-22610 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.x > > > TODO: generate email notifications including links to... > * jenkins job, > * diff files, and > * associated JIRA(s), plus > * instructions for how to build the TP locally. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-340) Cannot set a breakpoint in a node modules [EBZ#497685]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-340?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-340: ---------------------------- Sprint: devex #118 July 2016, devex #119 August 2016 (was: devex #118 July 2016) > Cannot set a breakpoint in a node modules [EBZ#497685] > ------------------------------------------------------ > > Key: ERT-340 > URL: https://issues.jboss.org/browse/ERT-340 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > Fix For: Neon.1 (4.6) > > > Created attachment 263019 > Simple project that demos the problem > When I debug my node application and I add a breakpoint in a file inside a "node_modules" folder, the code executes but the breakpoint does not halt the program execution. > Is this a supported feature? If not, is there workaround for this? > I attached the projects for reference. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-381) Can not select an array element in Outline view (it always re-select the parent) [EBZ#497253]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-381?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-381: ------------------------------- Assignee: Snjezana Peco > Can not select an array element in Outline view (it always re-select the parent) [EBZ#497253] > --------------------------------------------------------------------------------------------- > > Key: ERT-381 > URL: https://issues.jboss.org/browse/ERT-381 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Labels: bzira, wst.json > > Steps: > Create a JSON file with the following contents: > { > "thirdaddition": true, > "name": "JSONEditorTest2", > "secondaddition": 2, > "description": "JSONEditorTest description2", > "version": "1.0.1", > "main": "app.js", > "scripts": { > "start": "node app.js" > }, > "array_of_objects": [1, 2, 3], > "value": "test", > "anothervalue": "1234" > } > Navigate in Outline view and try to select there any of the elements in "array_of_objects". > Notice that Outline view does not allow you select any of those elements, selection is reset to the parent "array_of_objects" > Found on MacOS, but I can reproduce it on Windows too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-382) Adding a new value to the JSON file collapses the Outline view [EBZ#497260]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-382?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-382: ------------------------------- Assignee: Snjezana Peco > Adding a new value to the JSON file collapses the Outline view [EBZ#497260] > --------------------------------------------------------------------------- > > Key: ERT-382 > URL: https://issues.jboss.org/browse/ERT-382 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Labels: bzira, wst.json > > This is part of the improvements that the Outline view require for JSON Editor > Steps: > Create a JSON file with the following content: > { > "thirdaddition": true, > "name": "JSONEditorTest2", > "secondaddition": 2, > "description": "JSONEditorTest description2", > "version": "1.0.1", > "main": "app.js", > "scripts": { > "start": "node app.js" > }, > "anothervalue": 123 > } > Put the cursor before "anothervalue" (right after closing "scripts"), and type "value": "test", > Notice that right after entering the comma, the "Outline" view collapses. There is no reason for that to happen, the tree should be expanded and showing the recently inserted node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-383) JSONEditor: NPE when working with an array of objects [EBZ#497261]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-383?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-383: ------------------------------- Assignee: Snjezana Peco > JSONEditor: NPE when working with an array of objects [EBZ#497261] > ------------------------------------------------------------------ > > Key: ERT-383 > URL: https://issues.jboss.org/browse/ERT-383 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Labels: bzira, wst.json > > I have not been able to reproduce this consistently, but here it goes: > Create a JSON file with following content: > { > "thirdaddition": true, > "name": "JSONEditorTest2", > "secondaddition": 2, > "description": "JSONEditorTest description2", > "version": "1.0.1", > "main": "app.js", > "scripts": { > "start": "node app.js" > }, > "array_of_objects": [{"abc": 1234}, {"value": 1234 }]]}}}}}}]}], > "value": "test", > "anothervalue": "1234" > } > When adding and removing (invalid) closing brackets, then modifying the value of the second array element (value), I tend to see this exception: > java.lang.NullPointerException > at org.eclipse.wst.json.core.internal.document.JSONModelParser.changeAttrValue(JSONModelParser.java:89) > at org.eclipse.wst.json.core.internal.document.JSONModelParser.changeRegion(JSONModelParser.java:131) > at org.eclipse.wst.json.core.internal.document.JSONModelImpl.regionChanged(JSONModelImpl.java:654) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:542) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1180) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1964) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.eclipse.jface.text.projection.ProjectionTextStore.replace(ProjectionTextStore.java:103) > at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1094) > at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1119) > at org.eclipse.jface.text.projection.ProjectionDocument.replace(ProjectionDocument.java:625) > at org.eclipse.jface.text.DefaultDocumentAdapter.replaceTextRange(DefaultDocumentAdapter.java:233) > at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7374) > at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:8225) > at org.eclipse.swt.custom.StyledText.doBackspace(StyledText.java:2334) > at org.eclipse.swt.custom.StyledText.invokeAction(StyledText.java:7164) > at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:6022) > at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:6049) > at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5733) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4248) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1538) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1534) > at org.eclipse.swt.widgets.Canvas.sendKeyEvent(Canvas.java:515) > at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1090) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5817) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSResponder.interpretKeyEvents(NSResponder.java:68) > at org.eclipse.swt.widgets.Composite.keyDown(Composite.java:610) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5727) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) > at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2140) > at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2402) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5789) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5218) > at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5367) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3695) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4007) Need a new check for existing OpenJDK installed as an msi package

by Jan Richter (JIRA)

Jan Richter created JBDS-4007: --------------------------------- Summary: Need a new check for existing OpenJDK installed as an msi package Key: JBDS-4007 URL: https://issues.jboss.org/browse/JBDS-4007 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.1.0.AM3 Reporter: Jan Richter Assignee: Denis Golovin Now that OpenJDK is being installed using the msi installer, a new possible issue has arisen: Basically it's the same problem we had with Vagrant and Virtualbox - one cannot simply try to reinstall msi package into a different folder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016