[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21377:
---------------------------------------------
about when/how to provide it then for JBDS 9.1 I dont see an urgency for yaml when we currently use json almost anywhere for openshift.
Having json editor included would have a bigger impact.
For JBDS 10.x having yaml AND json I think make sense to include by default in same vain that we include xml support. both formats have "won" their own part of the various ecosystems.
But for now json is what is pushed most - thus yaml is secondary.
To start we at least need QE having resources to cover the basic testing.
> Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21377
> URL: https://issues.jboss.org/browse/JBIDE-21377
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: updatesite
> Affects Versions: 4.3.1.Beta1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
> Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, jbtcentral-p2diff_460.txt
>
>
> There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default.
> This would require adding it to the TP and adding a dependency from a JBT feature to it.
> On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny])
> --
> Story points - 8 (fibonacci):
> * update Central TP,
> * update JBT/JBDS TPs,
> * update JBT/JBDS category.xml files,
> * update JBDS feature.xml,
> * send announcement email re: TP changes
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21563) [regression] Explorer: Connection or (multiple) application deletion does not work anymore
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21563?page=com.atlassian.jira.plugi... ]
Rastislav Wagner edited comment on JBIDE-21563 at 1/25/16 7:33 AM:
-------------------------------------------------------------------
Pressing delete on keyboard does nothing in JBT 4.3.1.Beta2. I tried deleting project and server but Im unable to do so using delete key (context menu works).
This operation works as usually on clean Eclipse 4.5.2.RC1 and stopped working when I installed Openshift plugins. Seems to be connected to this issue.
was (Author: rawagner):
Pressing delete on keyboard does nothing in JBT 4.3.1.Beta2. I tried deleting project and server but Im unable to do so using delete key (context menu works).
This operation works as usually on clean Eclipse 4.5.2.RC1 and stopped working when I installed Openshift plugins. Seems to be that its connected to this issue.
> [regression] Explorer: Connection or (multiple) application deletion does not work anymore
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21563
> URL: https://issues.jboss.org/browse/JBIDE-21563
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: explorer, openshift_v2, respin-a
> Fix For: 4.3.1.Beta2, 4.3.1.CR1
>
>
> Previously it was possible to select multiple OpenShift 2 applications and delete them at once via context menu Delete application(s).... Currently there is no such context menu anymore and it is a pain to delete several applications one by one.
> Added by Slava: In my environment, Delete for objects of OpenShift 2 does not work at all (menu is shown, but nothing happens). It seems the cause is a slip in plugin.xml for Openshift 3, handler org.jboss.tools.openshift.internal.ui.handler.DeleteResourceHandler declared activeWhen with <or> (count==1 _or_ instanceof IResource). So, formally having a lot of restrictions but passing them, this handler imposes itself on all selections. Though, it is possible that the bug reveals not in all environments.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21563) [regression] Explorer: Connection or (multiple) application deletion does not work anymore
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21563?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-21563:
------------------------------------------
Pressing delete on keyboard does nothing in JBT 4.3.1.Beta2. I tried deleting project and server but Im unable to do so using delete key (context menu works).
This operation works as usually on clean Eclipse 4.5.2.RC1 and stopped working when I installed Openshift plugins. Seems to be that its connected to this issue.
> [regression] Explorer: Connection or (multiple) application deletion does not work anymore
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21563
> URL: https://issues.jboss.org/browse/JBIDE-21563
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: explorer, openshift_v2, respin-a
> Fix For: 4.3.1.Beta2, 4.3.1.CR1
>
>
> Previously it was possible to select multiple OpenShift 2 applications and delete them at once via context menu Delete application(s).... Currently there is no such context menu anymore and it is a pain to delete several applications one by one.
> Added by Slava: In my environment, Delete for objects of OpenShift 2 does not work at all (menu is shown, but nothing happens). It seems the cause is a slip in plugin.xml for Openshift 3, handler org.jboss.tools.openshift.internal.ui.handler.DeleteResourceHandler declared activeWhen with <or> (count==1 _or_ instanceof IResource). So, formally having a lot of restrictions but passing them, this handler imposes itself on all selections. Though, it is possible that the bug reveals not in all environments.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21398) EL var is not resolved correctly when value is set with bean method returning an array
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21398?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-21398.
-------------------------------
Verified with 9.1.0.Beta2-v20160122-0528-B256.
> EL var is not resolved correctly when value is set with bean method returning an array
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-21398
> URL: https://issues.jboss.org/browse/JBIDE-21398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, jsf
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.1.Beta2
>
>
> 1. Create a bean class with property returning array:
> {code}
> public SignOffStatus[] getStatuses() {
> return null;
> }
> {code}
> 2. Set collection value of an iterative tag with method call rather than property call
> {code}
> <p:selectOneMenu value="#{instancePage.instanceCriteria.status}">
> <f:selectItem itemLabel="--select--" itemValue="#{null}" />
> <f:selectItems value="#{appBean.getStatuses()}" var="stat" itemLabel="#{stat.label}" />
> </p:selectOneMenu>
> {code}
> 3. Failure: members of var are not resolved.
> If value is set with property call
> {code}
> value="#{appBean.statuses}"
> {code}
> and/or if method getStatuses() returns a collection type, then var members resolution works ok.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21338) Credential framework not working with my workspace
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21338?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-21338.
------------------------------
Verified in JBDS 9.1.0.Beta2. Closing.
> Credential framework not working with my workspace
> --------------------------------------------------
>
> Key: JBIDE-21338
> URL: https://issues.jboss.org/browse/JBIDE-21338
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Environment: JBD 9.1.0.Beta1-v20151212-0638-B189
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Fix For: 4.3.1.Beta2
>
>
> Today I noticed, that credentials framework stopped working with my workspace. Starting eclipse with fresh workspace, credentials framework works. I'm not aware what I did to break it ;-) It's just a workspace I use on daily basis. .metadata directory is attached.
> Some stacktraces:
> Selecting "JBoss Tools"->"Credentials" in preferences: Dialog saying "The currently displayed page contains invalid values." and error in error log:
> {noformat:title=Problems occurred when invoking code from plug-in: "org.eclipse.jface".}
> java.lang.NoClassDefFoundError: Could not initialize class org.jboss.tools.foundation.core.credentials.CredentialService
> at org.jboss.tools.foundation.ui.credentials.internal.CredentialPreferencePage$CredentialTreeContentProvider.getElements(CredentialPreferencePage.java:83)
> at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1000)
> at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:700)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1349)
> at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:353)
> at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:906)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:617)
> at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:815)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791)
> at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:611)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1541)
> at org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:790)
> at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1525)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1462)
> at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:366)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1423)
> at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1517)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:292)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1701)
> at org.jboss.tools.foundation.ui.credentials.internal.CredentialPreferencePage.createContents(CredentialPreferencePage.java:193)
> at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241)
> at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1450)
> at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:1217)
> 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.showPage(PreferenceDialog.java:1209)
> at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:608)
> at org.eclipse.jface.preference.PreferenceDialog$9$1.run(PreferenceDialog.java:675)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:670)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:877)
> 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.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:874)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1243)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1269)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1$2.run(OpenStrategy.java:440)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3794)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3433)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> 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:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {noformat}
> In DownloadRuntimesWizard, selecting server requiring credentials (like EAP 6.4 for example) and clicking next:
> {noformat:title=Unhandled event loop exception}
> java.lang.NoClassDefFoundError: Could not initialize class org.jboss.tools.foundation.core.credentials.CredentialService
> at org.jboss.tools.foundation.ui.credentials.ChooseCredentialComponent.findDomains(ChooseCredentialComponent.java:197)
> at org.jboss.tools.foundation.ui.credentials.ChooseCredentialComponent.<init>(ChooseCredentialComponent.java:72)
> at org.jboss.tools.foundation.ui.credentials.ChooseCredentialComposite.<init>(ChooseCredentialComposite.java:47)
> at org.jboss.tools.foundation.ui.credentials.ChooseCredentialComposite.<init>(ChooseCredentialComposite.java:36)
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.createCredentialComposite(DownloadManagerCredentialsFragment.java:123)
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.createComposite(DownloadManagerCredentialsFragment.java:115)
> at org.jboss.tools.foundation.ui.xpl.taskwizard.TaskWizardPage.createControl(TaskWizardPage.java:44)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1216)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1208)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1197)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1194)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885)
> at org.jboss.tools.foundation.ui.xpl.taskwizard.TaskWizardDialog.nextPressed(TaskWizardDialog.java:40)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.jboss.tools.runtime.ui.internal.preferences.RuntimePreferencePage$9.widgetSelected(RuntimePreferencePage.java:384)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> 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:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {noformat}
> .metadata directory is shared here: https://drive.google.com/a/redhat.com/file/d/0B8eagNTwMG5VMDFpWndOcmJlbGc...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21570) Fix ECMA5 content assist JUnit test
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-21570:
-----------------------------------
Summary: Fix ECMA5 content assist JUnit test
Key: JBIDE-21570
URL: https://issues.jboss.org/browse/JBIDE-21570
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: javascript
Affects Versions: 4.3.1.Beta1
Reporter: Denis Golovin
Assignee: Victor Rubezhny
Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
During CI build on jenkins JUnit I test fails. Filing test checks for ECMA5 related proposals in content assist for .js file in JavaScript project. With manually created project and .js file everything works as expected.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months