[JBoss JIRA] (JBIDE-19994) Shell supposed to containg existing applications for import does not contain any application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19994?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-19994:
----------------------------------
Attachment: import_app_shell.png
> Shell supposed to containg existing applications for import does not contain any application
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-19994
> URL: https://issues.jboss.org/browse/JBIDE-19994
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Attachments: import_app_shell.png
>
>
> When trying to import an existing application to the workspace via shell menu File - Import, there is opened OpenShift application wizard to import an existing application. After click on Browse button Select Existing Application shell is opened and there should be some applications/domains with applications, but the shell is empty.
> !import_app_shell.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19833) NPE after updating JVM Monitor preferences
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19833?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19833.
---------------------------------
Verified in JBDS 9.0.0.Beta1 B34
> NPE after updating JVM Monitor preferences
> ------------------------------------------
>
> Key: JBIDE-19833
> URL: https://issues.jboss.org/browse/JBIDE-19833
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> JBIDE-19530 improved validation of number fields in JVM Monitor preference window, but now I get a NPE when I apply changes.
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.jmx.jvmmonitor.internal.ui.JavaMonitorPreferencePage.applyChanges(JavaMonitorPreferencePage.java:161)
> at org.jboss.tools.jmx.jvmmonitor.internal.ui.JavaMonitorPreferencePage.performOkMonitor(JavaMonitorPreferencePage.java:150)
> at org.jboss.tools.jmx.jvmmonitor.internal.ui.JavaMonitorPreferencePage.performOk(JavaMonitorPreferencePage.java:137)
> at org.eclipse.jface.preference.PreferenceDialog$12.run(PreferenceDialog.java:928)
> 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:912)
> at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:410)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:168)
> at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:231)
> 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:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672)
> 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.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:59)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:196)
> at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler.runCommand(CocoaUIHandler.java:715)
> at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler.access$6(CocoaUIHandler.java:703)
> at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler$8.widgetSelected(CocoaUIHandler.java:568)
> 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:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> 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: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: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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> {code}
> When I try again, I even get some Unhandled event loop exception which is actually a NPE also:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.jmx.jvmmonitor.internal.ui.JavaMonitorPreferencePage.applyChanges(JavaMonitorPreferencePage.java:161)
> at org.jboss.tools.jmx.jvmmonitor.internal.ui.JavaMonitorPreferencePage.performOkMonitor(JavaMonitorPreferencePage.java:150)
> at org.jboss.tools.jmx.jvmmonitor.internal.ui.JavaMonitorPreferencePage.performOk(JavaMonitorPreferencePage.java:137)
> at org.eclipse.jface.preference.PreferencePage.performApply(PreferencePage.java:464)
> at org.eclipse.jface.preference.PreferencePage$2.widgetSelected(PreferencePage.java:294)
> 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:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672)
> 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.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:59)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:196)
> at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler.runCommand(CocoaUIHandler.java:715)
> at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler.access$6(CocoaUIHandler.java:703)
> at org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CocoaUIHandler$8.widgetSelected(CocoaUIHandler.java:568)
> 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:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> 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: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: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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> {code}
> I tried both JBoss Tools 4.3.0.Alpha2 and latest nightly of JBDS (jboss-devstudio-9.0.0.Beta1-v20150519-1626-B3243-installer-standalone.jar). Both on OS X.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3446) Add support for IzPack INSTALL_PATH property to predefine installation path
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3446?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3446:
-------------------------------------
Yeah, to be honest I'm not sure if there is even demand for this in JBDS. I reported this together with JIRAs for FSW and DV installers where would directly benefit from such functionality in JBDS. But for JBDS itself, I would take it more as a "nice to have" feature. (Yes, I know it was me who reported this ;)
> Add support for IzPack INSTALL_PATH property to predefine installation path
> ---------------------------------------------------------------------------
>
> Key: JBDS-3446
> URL: https://issues.jboss.org/browse/JBDS-3446
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Affects Versions: 8.1.0.GA
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 9.0.0.Beta2
>
>
> In a recent discussion around JBIDE-19852 , it was pointed out that IzPack supports supplying properties to the installer, so that some values are predefined.
> Details are here:
> http://docs.codehaus.org/display/IZPACK/Unattended+Installations
> The idea is that you could run this:
> java -DINSTALL_PATH=/default/path -jar installer.jar
> And this would pre-fill the installation path to the path given in the command.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19984) Wrong version of playground components
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19984?page=com.atlassian.jira.plugi... ]
Mickael Istria resolved JBIDE-19984.
------------------------------------
Resolution: Done
jbosstools-playground was branched, built, and then the build chain (jbosstools-central, aggregate, product) did run.
Both aggregation site and product seem to contain a Beta1 build of easymport bundles.
> Wrong version of playground components
> --------------------------------------
>
> Key: JBIDE-19984
> URL: https://issues.jboss.org/browse/JBIDE-19984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, easymport, updatesite
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Critical
> Labels: respin-a
> Fix For: 4.3.0.Beta1
>
>
> JBDS 9.0.0.beta1 build contains alpha2 easymport plugins
> org.jboss.tools.playground.easymport.javascript_1.0.0.Alpha2-v20150417-1604-B3.jar
> org.jboss.tools.playground.easymport.jee_1.0.0.Alpha2-v20150417-1604-B3.jar
> org.jboss.tools.playground.easymport.maven_1.0.0.Alpha2-v20150417-1604-B3.jar
> Also org.eclipse.e4.ui.importer.java_0.1.0.v20150414-1856.jar
> looks quite old but maybe nothing changed there.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19992) Open Properties view on double click of elemet in batch diagram
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-19992:
---------------------------------------
Summary: Open Properties view on double click of elemet in batch diagram
Key: JBIDE-19992
URL: https://issues.jboss.org/browse/JBIDE-19992
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: batch
Affects Versions: 4.3.0.Beta1
Reporter: Lucia Jelinkova
In batch editor diagram tab, it would be nice if after double click on some element (e.g. step) corrensponding Properties view would be open and activated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months