[JBoss JIRA] (JBDS-4065) DevStudio 1.1 Installer unfriendly when 1.0 present
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4065?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-4065:
------------------------------------
Assignee: Rob Stryker
> DevStudio 1.1 Installer unfriendly when 1.0 present
> ---------------------------------------------------
>
> Key: JBDS-4065
> URL: https://issues.jboss.org/browse/JBDS-4065
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, platform-installer
> Affects Versions: 10.1.0.GA
> Environment: Windows 10, DevSuite Installer 1.0 had been run
> Reporter: Rick Wagner
> Assignee: Rob Stryker
>
> When running the DevSuite 1.1 installer, DevStudio is not connected to the installed CDK.
> Observations:
> - All components removed before installation, does not help. (VirtualBox and Vagrant using Add/Remove programs, everything else directory-deleted, Environment variables cleaned).
> - DevStudio says it can't start the Container Development Environment server. ('Failed to find Vagrant!' reads the error). If I open Launch Configuration, it lists the Main as "C:\HashiCorp\Vagrant\bin\vagrant.exe", which is not in the installation directory.
> - It was noted that DevStudio marked itself 'completed' before Vagrant was installed. How does DevStudio know where Vagrant is?
> - It's noted that DevStudio 'remembers' user settings (i.e. CDK registration user/password) from previous attempts. Where is this information kept? I must've missed something in cleanup.
> - Tried full suite installation, then deleting DevStudio, then re-installing. (Hoping DevStudio would then find Vagrant in the right location, because it followed Vagrant's installation.) Result: No Container Development Environment server is present in 'server' view.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4065) DevStudio 1.1 Installer unfriendly when 1.0 present
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4065?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-4065:
---------------------------------
Component/s: cdk
platform-installer
(was: installer)
> DevStudio 1.1 Installer unfriendly when 1.0 present
> ---------------------------------------------------
>
> Key: JBDS-4065
> URL: https://issues.jboss.org/browse/JBDS-4065
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, platform-installer
> Affects Versions: 10.1.0.GA
> Environment: Windows 10, DevSuite Installer 1.0 had been run
> Reporter: Rick Wagner
>
> When running the DevSuite 1.1 installer, DevStudio is not connected to the installed CDK.
> Observations:
> - All components removed before installation, does not help. (VirtualBox and Vagrant using Add/Remove programs, everything else directory-deleted, Environment variables cleaned).
> - DevStudio says it can't start the Container Development Environment server. ('Failed to find Vagrant!' reads the error). If I open Launch Configuration, it lists the Main as "C:\HashiCorp\Vagrant\bin\vagrant.exe", which is not in the installation directory.
> - It was noted that DevStudio marked itself 'completed' before Vagrant was installed. How does DevStudio know where Vagrant is?
> - It's noted that DevStudio 'remembers' user settings (i.e. CDK registration user/password) from previous attempts. Where is this information kept? I must've missed something in cleanup.
> - Tried full suite installation, then deleting DevStudio, then re-installing. (Hoping DevStudio would then find Vagrant in the right location, because it followed Vagrant's installation.) Result: No Container Development Environment server is present in 'server' view.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4065) DevStudio 1.1 Installer unfriendly when 1.0 present
by Rick Wagner (JIRA)
[ https://issues.jboss.org/browse/JBDS-4065?page=com.atlassian.jira.plugin.... ]
Rick Wagner commented on JBDS-4065:
-----------------------------------
Through all these attempts, the CDK works from a Cygwin prompt. It's only DevStudio that's not getting the connection/server set up.
> DevStudio 1.1 Installer unfriendly when 1.0 present
> ---------------------------------------------------
>
> Key: JBDS-4065
> URL: https://issues.jboss.org/browse/JBDS-4065
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.1.0.GA
> Environment: Windows 10, DevSuite Installer 1.0 had been run
> Reporter: Rick Wagner
>
> When running the DevSuite 1.1 installer, DevStudio is not connected to the installed CDK.
> Observations:
> - All components removed before installation, does not help. (VirtualBox and Vagrant using Add/Remove programs, everything else directory-deleted, Environment variables cleaned).
> - DevStudio says it can't start the Container Development Environment server. ('Failed to find Vagrant!' reads the error). If I open Launch Configuration, it lists the Main as "C:\HashiCorp\Vagrant\bin\vagrant.exe", which is not in the installation directory.
> - It was noted that DevStudio marked itself 'completed' before Vagrant was installed. How does DevStudio know where Vagrant is?
> - It's noted that DevStudio 'remembers' user settings (i.e. CDK registration user/password) from previous attempts. Where is this information kept? I must've missed something in cleanup.
> - Tried full suite installation, then deleting DevStudio, then re-installing. (Hoping DevStudio would then find Vagrant in the right location, because it followed Vagrant's installation.) Result: No Container Development Environment server is present in 'server' view.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4065) DevStudio 1.1 Installer unfriendly when 1.0 present
by Rick Wagner (JIRA)
Rick Wagner created JBDS-4065:
---------------------------------
Summary: DevStudio 1.1 Installer unfriendly when 1.0 present
Key: JBDS-4065
URL: https://issues.jboss.org/browse/JBDS-4065
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: installer
Affects Versions: 10.1.0.GA
Environment: Windows 10, DevSuite Installer 1.0 had been run
Reporter: Rick Wagner
When running the DevSuite 1.1 installer, DevStudio is not connected to the installed CDK.
Observations:
- All components removed before installation, does not help. (VirtualBox and Vagrant using Add/Remove programs, everything else directory-deleted, Environment variables cleaned).
- DevStudio says it can't start the Container Development Environment server. ('Failed to find Vagrant!' reads the error). If I open Launch Configuration, it lists the Main as "C:\HashiCorp\Vagrant\bin\vagrant.exe", which is not in the installation directory.
- It was noted that DevStudio marked itself 'completed' before Vagrant was installed. How does DevStudio know where Vagrant is?
- It's noted that DevStudio 'remembers' user settings (i.e. CDK registration user/password) from previous attempts. Where is this information kept? I must've missed something in cleanup.
- Tried full suite installation, then deleting DevStudio, then re-installing. (Hoping DevStudio would then find Vagrant in the right location, because it followed Vagrant's installation.) Result: No Container Development Environment server is present in 'server' view.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (ERT-214) Validate JSON file with JSON Schema [EBZ#494111]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/ERT-214?page=com.atlassian.jira.plugin.sy... ]
Snjezana Peco updated ERT-214:
------------------------------
Sprint: devex #116 June 2016, devex #118 July 2016, devex #120 September 2016 (was: devex #116 June 2016, devex #118 July 2016, devex #121 October 2016)
> Validate JSON file with JSON Schema [EBZ#494111]
> ------------------------------------------------
>
> Key: ERT-214
> URL: https://issues.jboss.org/browse/ERT-214
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Source Editing
> Reporter: Friendly Jira Robot
> Assignee: Snjezana Peco
> Priority: Trivial
> Labels: bzira, wst.json
> Fix For: Neon.2 (4.6)
>
>
> It's a very big task, but it should be fantastic if WTP Validator could validate JSON file by using JSON Schema.
> To do that:
> * JSONSchemaDocument should support the full specification of JSON Schema.
> * minimal-json should be improved to collect line, column or perhaps we could use IJSONDocument to validate it with JSON Schema.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (ERT-387) JSON editor "supports" comments, not supported by JSON [EBZ#499705]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/ERT-387?page=com.atlassian.jira.plugin.sy... ]
Snjezana Peco updated ERT-387:
------------------------------
Sprint: devex #120 September 2016 (was: devex #121 October 2016)
> JSON editor "supports" comments, not supported by JSON [EBZ#499705]
> -------------------------------------------------------------------
>
> Key: ERT-387
> URL: https://issues.jboss.org/browse/ERT-387
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Source Editing
> Reporter: Friendly Jira Robot
> Assignee: Snjezana Peco
> Priority: Trivial
> Labels: bzira, wst.json
> Fix For: Neon.2 (4.6)
>
>
> I tried commenting a line in a JSON file using the common syntax "/* comment */":
> /*"jquery/jquery-min": "1.12",*/
> This caused the line to become blue, so I figured JSON must support comments. But as mentioned in https://en.wikipedia.org/w/index.php?title=JSON&oldid=734431215 this is not the case.
> Ticket #495578 explains that Angelo ZERR decided to support "JSON comments" since .jshintrc (no idea what that is) uses it. In my opinion, this should be disabled by default, but for sure, it should be possible to disable. Currently, all JSON highlights are mandatory (the checkboxes are disabled).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (ERT-412) Need to improve as-you-type formatting for JSON editor [EBZ#501011]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/ERT-412?page=com.atlassian.jira.plugin.sy... ]
Snjezana Peco updated ERT-412:
------------------------------
Sprint: devex #120 September 2016 (was: devex #121 October 2016)
> Need to improve as-you-type formatting for JSON editor [EBZ#501011]
> -------------------------------------------------------------------
>
> Key: ERT-412
> URL: https://issues.jboss.org/browse/ERT-412
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Source Editing
> Reporter: Friendly Jira Robot
> Assignee: Snjezana Peco
> Labels: bzira, wst.json
> Fix For: Neon.2 (4.6)
>
>
> Need to improve as-you-type formatting in JSON editor for curly braces:
> 1. "dependencies" : {|}
> 2. "dependencies" : {
> |
> }
> | - represents cursor position
> 1 - represents state before hitting Enter
> 2 - represents state after hitting Enter
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (ERT-383) JSONEditor: NPE when working with an array of objects [EBZ#497261]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/ERT-383?page=com.atlassian.jira.plugin.sy... ]
Snjezana Peco updated ERT-383:
------------------------------
Sprint: devex #120 September 2016 (was: devex #121 October 2016)
> 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
> Fix For: Neon.2 (4.6)
>
>
> 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, 6 months