[JBoss JIRA] (JBIDE-18274) AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18274?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18274:
-------------------------------------
I can't replicate =/ Tried same steps, hostname rawbdor, oracle jdk 1.7.0_57
> AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18274
> URL: https://issues.jboss.org/browse/JBIDE-18274
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.2.2.Final, 4.3.0.Alpha1
>
> Attachments: server-adapter.png, server-editor.png, server-logs.png, server-runtime.png
>
>
> This is a follow up of JBIDE-17935 .
> Previously, Rob fixed this:
> {quote}
> I've surprisingly been able to replicate this and it's a race-condition. I'll need to synchronize some variables in this class here.
> {quote}
> But in this rare case it still fails for me.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBIDE-18907) Improve handling of inaccessible remote server [mgmt]
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18907?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-18907.
---------------------------------
Resolution: Done
It would be unreasonable to check *everything* about the server in the launch configuration. The standard workflow is that we execute a command (unless externally managed is checked) and then fire a poller. The poller just responds that the polling mechanism works.
I've committed a change to master, and what this change does is ensure that at least the poller is checked. In the past, if 'externally managed' was checked, we didn't even do this. We simply assumed the server was started.
Since we're no longer "assuming" the server is started, I've also changed the externally managed string to read "Server lifecycle is externally managed." since we are no longer "assuming" it is started.
> Improve handling of inaccessible remote server [mgmt]
> -----------------------------------------------------
>
> Key: JBIDE-18907
> URL: https://issues.jboss.org/browse/JBIDE-18907
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha1
>
> Attachments: remote-connection-error.png
>
>
> With JBIDE-18513, it is now possible to set up a server that does not require any runtime at all (local or remote). The server setup is: remote, management operations, externally managed, no local runtime.
> When I tried it today, I started the server on the remote machine and then marked the server in eclipse as started. Then I wanted to deploy a project and got an error:
> !remote-connection-error.png!
> The underlying error is:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.core 4 0 2014-12-09 13:37:52.037
> !MESSAGE JBossTools is unable to verify that the server is up and responsive.
> !STACK 0
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.execute(Wildfly8Manager.java:333)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.getServerState(Wildfly8Manager.java:263)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8ManagerService.getServerState(Wildfly8ManagerService.java:142)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.getServerState(JBoss7ManagerServiceProxy.java:71)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.isRunning(ManagementPublishController.java:113)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.canPublishInternal(ManagementPublishController.java:136)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.publishStart(ManagementPublishController.java:152)
> at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.publishStart(DeployableServerBehavior.java:104)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.execute(Wildfly8Manager.java:322)
> ... 12 more
> Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 14 more
> {code}
> It turned out that I forgot to setup the management port when I started the server on the server - I needed to add {code}-Djboss.bind.address.management=marvin{code}. With this it worked.
> My suggestion is that the tooling could check if the connection can be established when you press Start on the server.
> But it's just a suggestion - feel free to dismiss this idea ;)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBIDE-18591) "Error while JSDT ClassPath changed" exception occurs when creating thym project
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18591?page=com.atlassian.jira.plugi... ]
Pavol Srna closed JBIDE-18591.
------------------------------
Verified in JBT 4.2.1.CR1a build.
> "Error while JSDT ClassPath changed" exception occurs when creating thym project
> --------------------------------------------------------------------------------
>
> Key: JBIDE-18591
> URL: https://issues.jboss.org/browse/JBIDE-18591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Final
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 4.2.1.CR1
>
>
> Error message is "Error while JSDT ClassPath changed." and stacktrace is:
> {code}org.eclipse.core.internal.resources.ResourceException: The resource tree is locked for modifications.
> at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:116)
> at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2251)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1322)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1376)
> at tern.eclipse.ide.core.TernNature.configure(TernNature.java:59)
> at tern.eclipse.ide.internal.core.IDETernProject.ensureNatureIsConfigured(IDETernProject.java:817)
> at tern.eclipse.ide.internal.core.IDETernProject.<init>(IDETernProject.java:111)
> at tern.eclipse.ide.internal.core.IDETernProject.getTernProject(IDETernProject.java:134)
> at tern.eclipse.ide.core.TernCorePlugin.getTernProject(TernCorePlugin.java:99)
> at tern.eclipse.ide.jsdt.internal.JSDTClassPathManager.elementChanged(JSDTClassPathManager.java:67)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1591)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1581)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.firePostChangeDelta(DeltaProcessor.java:1416)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1392)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1945)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:389)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
> at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
> at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:378)
> at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1498)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
> at org.eclipse.wst.jsdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:807)
> at org.eclipse.wst.jsdt.internal.core.JavaProject.setRawIncludepath(JavaProject.java:2992)
> at org.eclipse.wst.jsdt.internal.core.JavaProject.setRawIncludepath(JavaProject.java:3023)
> at org.eclipse.thym.ui.wizard.project.HybridProjectCreator.setUpJavaScriptProject(HybridProjectCreator.java:135)
> at org.eclipse.thym.ui.wizard.project.HybridProjectCreator.createProject(HybridProjectCreator.java:104)
> at org.eclipse.thym.ui.wizard.project.HybridProjectCreator.createBasicTemplatedProject(HybridProjectCreator.java:78)
> at org.eclipse.thym.ui.wizard.project.NewHybridProjectWizard$1.run(NewHybridProjectWizard.java:91)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1059)
> at org.eclipse.thym.ui.wizard.project.NewHybridProjectWizard.performFinish(NewHybridProjectWizard.java:103)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438)
> 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:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.jboss.tools.central.editors.GettingStartedPage.openWizard(GettingStartedPage.java:697)
> at org.jboss.tools.central.editors.GettingStartedPage.access$14(GettingStartedPage.java:682)
> at org.jboss.tools.central.editors.GettingStartedPage$7.linkActivated(GettingStartedPage.java:636)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> 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:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438){code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBIDE-18907) Improve handling of inaccessible remote server [mgmt]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18907?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-18907:
---------------------------------------
Rob created this PR:
https://github.com/jbosstools/jbosstools-server/pull/314
The fix ensures that startup pollers are used for Externally managed servers. So a server using management poller should also prompt for the password (if it's wrong?). I will need to verify that.
> Improve handling of inaccessible remote server [mgmt]
> -----------------------------------------------------
>
> Key: JBIDE-18907
> URL: https://issues.jboss.org/browse/JBIDE-18907
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha1
>
> Attachments: remote-connection-error.png
>
>
> With JBIDE-18513, it is now possible to set up a server that does not require any runtime at all (local or remote). The server setup is: remote, management operations, externally managed, no local runtime.
> When I tried it today, I started the server on the remote machine and then marked the server in eclipse as started. Then I wanted to deploy a project and got an error:
> !remote-connection-error.png!
> The underlying error is:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.core 4 0 2014-12-09 13:37:52.037
> !MESSAGE JBossTools is unable to verify that the server is up and responsive.
> !STACK 0
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.execute(Wildfly8Manager.java:333)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.getServerState(Wildfly8Manager.java:263)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8ManagerService.getServerState(Wildfly8ManagerService.java:142)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.getServerState(JBoss7ManagerServiceProxy.java:71)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.isRunning(ManagementPublishController.java:113)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.canPublishInternal(ManagementPublishController.java:136)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementPublishController.publishStart(ManagementPublishController.java:152)
> at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.publishStart(DeployableServerBehavior.java:104)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:942)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.ide.eclipse.as.internal.management.wildfly8.Wildfly8Manager.execute(Wildfly8Manager.java:322)
> ... 12 more
> Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://MARVIN:9990. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 14 more
> {code}
> It turned out that I forgot to setup the management port when I started the server on the server - I needed to add {code}-Djboss.bind.address.management=marvin{code}. With this it worked.
> My suggestion is that the tooling could check if the connection can be established when you press Start on the server.
> But it's just a suggestion - feel free to dismiss this idea ;)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBIDE-18843) Only one error/warning is displayed in DownloadRuntimesWizard on install/dl selection page
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18843?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-18843.
------------------------------
Verified in JBDS 8.0.1.CR1a. Closing.
> Only one error/warning is displayed in DownloadRuntimesWizard on install/dl selection page
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-18843
> URL: https://issues.jboss.org/browse/JBIDE-18843
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.1.CR1
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Priority: Minor
> Labels: respin-a
> Fix For: 4.2.1.CR1
>
>
> This is followup of JBIDE-17213.
> Now, when user sets up non writable install folder and non existing download folder (or the other way around), warning is displayed and Finish is enabled.
> Instead of this, error should be displayed and Finish button should be disabled. If it isn't possible to show both warning and error in the same time, I'd like to see errors prioritized before warnings (warning is shown when error is resolved).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBIDE-18918) CLONE - Only one error/warning is displayed in DownloadRuntimesWizard on install/dl selection page
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18918?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-18918:
-------------------------------
Fix Version/s: (was: 4.2.1.CR1)
> CLONE - Only one error/warning is displayed in DownloadRuntimesWizard on install/dl selection page
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18918
> URL: https://issues.jboss.org/browse/JBIDE-18918
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.1.CR1
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.0.Alpha1
>
>
> This is followup of JBIDE-17213.
> Now, when user sets up non writable install folder and non existing download folder (or the other way around), warning is displayed and Finish is enabled.
> Instead of this, error should be displayed and Finish button should be disabled. If it isn't possible to show both warning and error in the same time, I'd like to see errors prioritized before warnings (warning is shown when error is resolved).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months
[JBoss JIRA] (JBIDE-18918) CLONE - Only one error/warning is displayed in DownloadRuntimesWizard on install/dl selection page
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18918?page=com.atlassian.jira.plugi... ]
Radim Hopp resolved JBIDE-18918.
--------------------------------
Resolution: Done
> CLONE - Only one error/warning is displayed in DownloadRuntimesWizard on install/dl selection page
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18918
> URL: https://issues.jboss.org/browse/JBIDE-18918
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.1.CR1
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.0.Alpha1
>
>
> This is followup of JBIDE-17213.
> Now, when user sets up non writable install folder and non existing download folder (or the other way around), warning is displayed and Finish is enabled.
> Instead of this, error should be displayed and Finish button should be disabled. If it isn't possible to show both warning and error in the same time, I'd like to see errors prioritized before warnings (warning is shown when error is resolved).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 6 months