[JBoss JIRA] (JBIDE-19820) Batch feature makes wildfly import way slower
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19820?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-19820.
-----------------------------------
Closing the issue.
[~rawagner], please reopen if the issue is not fixed.
> Batch feature makes wildfly import way slower
> ---------------------------------------------
>
> Key: JBIDE-19820
> URL: https://issues.jboss.org/browse/JBIDE-19820
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.0.Alpha2
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> I made a comparison between Eclipse M6 and Eclipse M6 with batch feature installed while importing wildfly. WF is imported as maven project, maven is set to offline mode and local repository contains all needed dependencies.
> I did a 4 runs with following results:
> M6 was able to import WF 628,575,577,612 (in seconds) = average 598s
> M6 with batch feature: 843,832,924,877 (in seconds) = average 869s
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20309) Link to website to create a new OpenShift account does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20309?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-20309.
---------------------------------
Verified in JBDS 9.0.0.Beta2 build ID Beta2-v20150726-0459-B93
> Link to website to create a new OpenShift account does not work
> ---------------------------------------------------------------
>
> Key: JBIDE-20309
> URL: https://issues.jboss.org/browse/JBIDE-20309
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: connection_wizard, respin-b
> Fix For: 4.3.0.Beta2
>
>
> Link "If you do not have an account on OpenShift, please sign up here." in New Connection dialog does not work. After click it cause unhandled event loop exception with following stack trace:
> {code}
> java.lang.IncompatibleClassChangeError: Expecting non-static method org.jboss.tools.foundation.ui.util.BrowserUtility.checkedCreateInternalBrowser(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/core/runtime/ILog;)V
> at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$4.widgetSelected(ConnectionWizardPage.java:241)
> 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:1327)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1351)
> at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1465)
> at org.eclipse.swt.widgets.Link.gtk_button_release_event(Link.java:372)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1945)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5590)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4717)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9272)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1225)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2422)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:244)
> at org.jboss.tools.openshift.internal.common.ui.command.NewConnectionHandler.execute(NewConnectionHandler.java:29)
> 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.GeneratedMethodAccessor89.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> 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:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> 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:1327)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20311) Cannot Show in Web Browser any OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20311?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-20311.
---------------------------------
Resolution: Done
Issue was solved by correct build flow.
Verified in JBDS 9.0.0.Beta2 Build ID Beta2-v20150726-0459-B93
> Cannot Show in Web Browser any OpenShift application
> ----------------------------------------------------
>
> Key: JBIDE-20311
> URL: https://issues.jboss.org/browse/JBIDE-20311
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.3.0.Beta2
>
>
> Trying to Show in - Web Browser OpenShift applications causes error in tooling. It is similar error for all use cases showing in browser.
> Error for Show in - Web Browser opened via context menu of a project:
> {code}
> java.lang.IncompatibleClassChangeError: Expecting non-static method org.jboss.tools.foundation.ui.util.BrowserUtility.checkedCreateInternalBrowser(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/core/runtime/ILog;)V
> at org.jboss.tools.openshift.internal.ui.handler.OpenInWebBrowserHandler.openBrowser(OpenInWebBrowserHandler.java:87)
> at org.jboss.tools.openshift.internal.ui.handler.OpenInWebBrowserHandler.access$0(OpenInWebBrowserHandler.java:80)
> at org.jboss.tools.openshift.internal.ui.handler.OpenInWebBrowserHandler$1.updateUI(OpenInWebBrowserHandler.java:67)
> at org.jboss.tools.openshift.internal.common.ui.job.UIUpdatingJob$1$1.runInUIThread(UIUpdatingJob.java:36)
> at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:97)
> 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.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)
> {code}
> And error for Show in - Web Browser opened from context menu of a routing:
> {code}
> java.lang.IncompatibleClassChangeError: Expecting non-static method org.jboss.tools.foundation.ui.util.BrowserUtility.checkedCreateInternalBrowser(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/core/runtime/ILog;)V
> at org.jboss.tools.openshift.internal.ui.handler.OpenInWebBrowserHandler.openBrowser(OpenInWebBrowserHandler.java:87)
> at org.jboss.tools.openshift.internal.ui.handler.OpenInWebBrowserHandler.execute(OpenInWebBrowserHandler.java:43)
> 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.GeneratedMethodAccessor89.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> 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:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> 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:1327)
> 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)
> {code}
> Show In - Web Browser via context menu of an application (v2).
> {code}
> java.lang.IncompatibleClassChangeError: Expecting non-static method org.jboss.tools.foundation.ui.util.BrowserUtility.checkedCreateInternalBrowser(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/core/runtime/ILog;)V
> at org.jboss.tools.openshift.express.internal.ui.command.OpenInWebBrowserHandler.execute(OpenInWebBrowserHandler.java:38)
> 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.GeneratedMethodAccessor89.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> 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:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> 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:1327)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TOOLSDOC-669) Document the consequences of creating a remote server without a runtime
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-669?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-669:
------------------------------------
Hi [~mmalina], could you review the added note here and let me know if you have any feedback? Once the text is finalized, I'll add it to the JBT version of this article as well:
https://access.redhat.com/articles/1515503
> Document the consequences of creating a remote server without a runtime
> -----------------------------------------------------------------------
>
> Key: TOOLSDOC-669
> URL: https://issues.jboss.org/browse/TOOLSDOC-669
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: General documentation issues
> Affects Versions: 4.3.0.Beta2
> Reporter: Martin Malina
> Assignee: Misha Ali
>
> In a recent discussion in JBIDE-19463, we talked about some limitations that result from creating of a remote server without a runtime.
> For example, the jmx connection does not work because we use libs from the runtime to connect via jmx.
> We have this document about setting up a remote server:
> https://access.redhat.com/articles/1515503
> There is this:
> {quote}
> d. A remote server can now be created without assigning a runtime to it. Depending on the requirements, select the Assign a runtime to this server check box (and select an existing runtime or create a new one) or leave the box unselected and then click Next.
> {quote}
> So I think it would make sense to add these details somewhere in there.
> From JBIDE-19463:
> {quote}
> Autodetection of ports by scanning your standalone.xml (or your selected configuration file). Since there's no local runtime, and no local standalone.xml, we can't notice that you've modified your ports to be non-standard.
> Also, without a local runtime, some small behavior changes might be default values. For example, sometimes we hard-code different behavior between minor or micro versions if we notice there's a bug in some previous release. For example, some of the early jboss-7 releases didn't support the -b flag.
> Without a local runtime to scan, we can't know the exact version you're running against, and can't customize args (or other things) to work around bugs in those specific runtime versions.
> {quote}
> On top of that, you won't be able to create a JMX connection to the server.
> I'll leave it to you to decide how much details we need in the article. Maybe it's not necessary to talk about early versions of jboss-7 and that part. But it makes sense to at least mention that some things may be missing, mainly JMX connection, detection of ports from standalone.xml and perhaps several more.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBDS-3492) JBDS app icon and installer icon are not the same
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3492?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3492:
-----------------------------
Attachment: jbds-installer-vs-installer-jbds-icon-status-bar.png
Here's how JBDS (with JBoss Central open) compares to the installer, when both are running in the task bar:
!jbds-installer-vs-installer-jbds-icon-status-bar.png!
> JBDS app icon and installer icon are not the same
> -------------------------------------------------
>
> Key: JBDS-3492
> URL: https://issues.jboss.org/browse/JBDS-3492
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta2
> Environment: Fedora 20 (Linux t540p-fc20-vm01.redhat.com 3.17.4-200.fc20.x86_64 #1 SMP Fri Nov 21 23:26:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux)
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Attachments: jbds-installer-vs-installer-jbds-icon-status-bar.png, jbds-installer-vs-installer-jbds-icon.png
>
>
> The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it.
> Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app.
> This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually.
> Screenshot showing an installer dialog superimposed over JBDS:
> !jbds-installer-vs-installer-jbds-icon.png!
> Should we change this?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBDS-3492) JBDS app icon and installer icon are not the same
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3492?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3492:
-----------------------------
Description:
The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it.
Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app.
This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually.
Screenshot showing an installer dialog superimposed over JBDS:
!jbds-installer-vs-installer-jbds-icon.png!
Should we change this?
was:
The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it.
Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app.
This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually.
> JBDS app icon and installer icon are not the same
> -------------------------------------------------
>
> Key: JBDS-3492
> URL: https://issues.jboss.org/browse/JBDS-3492
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Attachments: jbds-installer-vs-installer-jbds-icon.png
>
>
> The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it.
> Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app.
> This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually.
> Screenshot showing an installer dialog superimposed over JBDS:
> !jbds-installer-vs-installer-jbds-icon.png!
> Should we change this?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBDS-3492) JBDS app icon and installer icon are not the same
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3492?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3492:
-----------------------------
Environment:
Fedora 20 (Linux t540p-fc20-vm01.redhat.com 3.17.4-200.fc20.x86_64 #1 SMP Fri Nov 21 23:26:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux)
> JBDS app icon and installer icon are not the same
> -------------------------------------------------
>
> Key: JBDS-3492
> URL: https://issues.jboss.org/browse/JBDS-3492
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta2
> Environment: Fedora 20 (Linux t540p-fc20-vm01.redhat.com 3.17.4-200.fc20.x86_64 #1 SMP Fri Nov 21 23:26:41 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux)
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Attachments: jbds-installer-vs-installer-jbds-icon.png
>
>
> The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it.
> Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app.
> This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually.
> Screenshot showing an installer dialog superimposed over JBDS:
> !jbds-installer-vs-installer-jbds-icon.png!
> Should we change this?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBDS-3492) JBDS app icon and installer icon are not the same
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3492?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3492:
-----------------------------
CDW docs_ack: ?
CDW devel_ack: ?
CDW pm_ack: +
CDW qa_ack: ?
CDW release: ?
> JBDS app icon and installer icon are not the same
> -------------------------------------------------
>
> Key: JBDS-3492
> URL: https://issues.jboss.org/browse/JBDS-3492
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Attachments: jbds-installer-vs-installer-jbds-icon.png
>
>
> The icon used for the installer is a more-or-less solid red ball, but the icon for the JBDS app is a red ball with while circles through it.
> Unless this is a quirk of the way that izpack compresses/displays the icon, we may be using a different one for the installer than the app.
> This may also be an intentional design choice, so that if you're running JBDS and an installer you can tell which is which visually.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months