[JBoss JIRA] (JBIDE-23041) Restore Defaults preferences causes exception
by Rastislav Wagner (JIRA)
Rastislav Wagner created JBIDE-23041:
----------------------------------------
Summary: Restore Defaults preferences causes exception
Key: JBIDE-23041
URL: https://issues.jboss.org/browse/JBIDE-23041
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: visual-page-editor-core
Affects Versions: 4.4.1.AM3
Reporter: Rastislav Wagner
Fix For: 4.4.1.Final
{code}
java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Boolean
at org.jboss.tools.vpe.preview.editor.VpvEditor$5.propertyChange(VpvEditor.java:328)
at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:350)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:346)
at org.eclipse.ui.preferences.ScopedPreferenceStore.setToDefault(ScopedPreferenceStore.java:543)
at org.eclipse.jface.preference.FieldEditor.store(FieldEditor.java:674)
at org.eclipse.jface.preference.FieldEditorPreferencePage.performOk(FieldEditorPreferencePage.java:344)
at org.jboss.tools.vpe.editor.preferences.VpePreferencesPage.performOk(VpePreferencesPage.java:215)
at org.jboss.tools.common.model.ui.preferences.TabbedPreferencesPage.performOk(TabbedPreferencesPage.java:161)
at org.eclipse.jface.preference.PreferenceDialog$8.run(PreferenceDialog.java:905)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:889)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:409)
at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:168)
at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:230)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
at org.eclipse.jface.window.Window.open(Window.java:794)
at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211)
at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
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)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-339) Array initializer auto-formatting is a hideous, broken nightmare [EBZ#419931]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-339?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk resolved ERT-339.
-----------------------------
Resolution: Done
> Array initializer auto-formatting is a hideous, broken nightmare [EBZ#419931]
> -----------------------------------------------------------------------------
>
> Key: ERT-339
> URL: https://issues.jboss.org/browse/ERT-339
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Shane Bryzak
> Labels: General, bzira
> Fix For: Neon.1 (4.6)
>
>
> If you are writing an array initializer in JavaScript, you most likely want to it to look like this:
> var myArray = [
> item1,
> item2,
> item3,
> ...
> ];
> However, no matter how you configure Eclipse to format array initializers, it ignores it all and instead tries to make you kill yourself with frustration.
> Actually *typing* an array initializer goes like this, cursor position indicated by _
> 1. You type the following:
> var myArray = [_
> 2. Eclipse inserts a closing paren:
> var myArray = [_]
> 3. You press enter, expecting to a get a newline, but instead Eclipse interprets it as "move the cursor to the end of the line:
> var myArray = []_
> 4. You left-arrow the cursor back a position, and press enter again. This time, Eclipse does insert a newline. But it auto-indents as follows:
> var myArray = [
> _]
> Rather than following the same, sane behaviour it provides for object initializers, Eclipse idents the following line to the same column as the opening paren, it idents using spaces, even if you've configured it to use tabs and only tabs for indentation, and it leaves the closing paren on the same line, rather than moving it to the start of the next.
> Trying to fix the indentation is impossible, because it has used spaces instead of tabs. If you delete the spaces and press tab, it merely re-inserts the spaces and re-indents back to the column of the open paren!
> It's hard to adequately emphasise what a frustrating, poisonous impression this makes on someone using Eclipse as a tool for JavaScript development. It feels actively user-hostile.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-338) [formatter] Unwanted alignment on Enter when inside array literal [EBZ#356606]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-338?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk resolved ERT-338.
-----------------------------
Resolution: Done
> [formatter] Unwanted alignment on Enter when inside array literal [EBZ#356606]
> ------------------------------------------------------------------------------
>
> Key: ERT-338
> URL: https://issues.jboss.org/browse/ERT-338
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Shane Bryzak
> Labels: Future, General, bzira
> Fix For: Neon.1 (4.6)
>
>
> Eclipse 3.7 (I20110613-1736)
> JSDT 1.3.0 (20110527214303)
> WTP 3.3.0 (20100921193530)
> 1. Create a new JavaScript file and add this code:
> function() {
> var myArray = [];
> }
> 2. Put the editing caret between the square brackets, and press Enter.
> 3. You get
> function() {
> var myArray = [
> ];
> }
> Inside array literals, pressing Enter causes the editor to insert spaces to align the new line with the opening [ bracket. I expected it to just increase the indentation level.
> This happens when using a new workspace with all the default preference settings.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[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 resolved ERT-340.
-----------------------------
Resolution: Done
> 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
[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19911:
----------------------------------------
[~ppitonak] We need to be able to automatically create pull request to the jbosstools-target-platforms repo, using the rhdevelopers-ci account. So we need 1. rhdevelopers-ci to have a clone/fork of jbosstools-target-platform repo and 2. To have an API token that allows to push commits to new branch and create pull request.
> Create a (manual) job to update a given 3rd-party project on TP
> ---------------------------------------------------------------
>
> Key: JBIDE-19911
> URL: https://issues.jboss.org/browse/JBIDE-19911
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Mickael Istria
> Fix For: 4.4.x
>
>
> For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request.
> * Input: sourceSite, initialMirror (as found in .target), targetMirror
> * Then
> ** job mirros the sourceSite
> ** job publishes (scp) it to targetMirror
> ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target
> ** job runs "mvn fix-version ..." on multiple/*.target
> ** "mvn clean verify -Pmultiple2repo" on multiple/*.target
> ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER
> ** p2diff
> ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ]
Pavol Pitonak commented on JBIDE-19911:
---------------------------------------
[~mickael_istria] both me and Pavol Srna have credentials for Github account rhdevelopers-ci, just let me know what you need to do and I'll do it. Existing token might not have sufficient permissions, if that is a case, it's easy to create a new token just for this use-case.
> Create a (manual) job to update a given 3rd-party project on TP
> ---------------------------------------------------------------
>
> Key: JBIDE-19911
> URL: https://issues.jboss.org/browse/JBIDE-19911
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Mickael Istria
> Fix For: 4.4.x
>
>
> For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request.
> * Input: sourceSite, initialMirror (as found in .target), targetMirror
> * Then
> ** job mirros the sourceSite
> ** job publishes (scp) it to targetMirror
> ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target
> ** job runs "mvn fix-version ..." on multiple/*.target
> ** "mvn clean verify -Pmultiple2repo" on multiple/*.target
> ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER
> ** p2diff
> ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months