[JBoss JIRA] (ERT-88) Exception when checking package.json/bower.json [EBZ#488648]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-88?page=com.atlassian.jira.plugin.sys... ]
Ilya Buziuk reassigned ERT-88:
------------------------------
Assignee: Ilya Buziuk
> Exception when checking package.json/bower.json [EBZ#488648]
> ------------------------------------------------------------
>
> Key: ERT-88
> URL: https://issues.jboss.org/browse/ERT-88
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Ilya Buziuk
> Labels: General, bzira
>
> The following exception is logged when a project is closed.
> !ENTRY org.eclipse.wst.jsdt.js.npm 4 0 2016-02-28 10:15:30.039
> !MESSAGE Resource '/AprokectTor' is not open.
> !STACK 1
> org.eclipse.core.internal.resources.ResourceException: Resource '/AprokectTor' is not open.
> at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:144)
> at org.eclipse.core.internal.resources.Container.members(Container.java:239)
> at org.eclipse.core.internal.resources.Container.members(Container.java:226)
> at org.eclipse.wst.jsdt.js.common.util.WorkbenchResourceUtil.findFileRecursively(WorkbenchResourceUtil.java:166)
> at org.eclipse.wst.jsdt.js.npm.util.NpmUtil.isPackageJsonExist(NpmUtil.java:41)
> at org.eclipse.wst.jsdt.js.npm.internal.launch.tester.NpmLaunchTester.test(NpmLaunchTester.java:37)
> at org.eclipse.core.internal.expressions.Property.test(Property.java:58)
> at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:100)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:112)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:160)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:75)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:55)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.evalEnablementExpression(LaunchShortcutExtension.java:281)
> at org.eclipse.debug.ui.actions.ContextualLaunchAction.isApplicable(ContextualLaunchAction.java:287)
> at org.eclipse.debug.ui.actions.ContextualLaunchAction.fillMenu(ContextualLaunchAction.java:218)
> at org.eclipse.debug.ui.actions.ContextualLaunchAction$1.menuShown(ContextualLaunchAction.java:141)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4245)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313)
> at org.eclipse.jface.action.ActionContributionItem.copyMenu(ActionContributionItem.java:1243)
> at org.eclipse.jface.action.ActionContributionItem.handleShowProxy(ActionContributionItem.java:1223)
> at org.eclipse.jface.action.ActionContributionItem.lambda$7(ActionContributionItem.java:1186)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4245)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1505)
> at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:805)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5761)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:77)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:267)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:4146)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3688)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1118)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1019)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:691)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java: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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
> !SUBENTRY 1 org.eclipse.core.resources 4 372 2016-02-28 10:15:30.039
> !MESSAGE Resource '/AprokectTor' is not open.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ERT-88) Exception when checking package.json/bower.json [EBZ#488648]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-88?page=com.atlassian.jira.plugin.sys... ]
Ilya Buziuk resolved ERT-88.
----------------------------
Resolution: Done
> Exception when checking package.json/bower.json [EBZ#488648]
> ------------------------------------------------------------
>
> Key: ERT-88
> URL: https://issues.jboss.org/browse/ERT-88
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Ilya Buziuk
> Labels: General, bzira
>
> The following exception is logged when a project is closed.
> !ENTRY org.eclipse.wst.jsdt.js.npm 4 0 2016-02-28 10:15:30.039
> !MESSAGE Resource '/AprokectTor' is not open.
> !STACK 1
> org.eclipse.core.internal.resources.ResourceException: Resource '/AprokectTor' is not open.
> at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:144)
> at org.eclipse.core.internal.resources.Container.members(Container.java:239)
> at org.eclipse.core.internal.resources.Container.members(Container.java:226)
> at org.eclipse.wst.jsdt.js.common.util.WorkbenchResourceUtil.findFileRecursively(WorkbenchResourceUtil.java:166)
> at org.eclipse.wst.jsdt.js.npm.util.NpmUtil.isPackageJsonExist(NpmUtil.java:41)
> at org.eclipse.wst.jsdt.js.npm.internal.launch.tester.NpmLaunchTester.test(NpmLaunchTester.java:37)
> at org.eclipse.core.internal.expressions.Property.test(Property.java:58)
> at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:100)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:112)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:160)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:75)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:55)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.evalEnablementExpression(LaunchShortcutExtension.java:281)
> at org.eclipse.debug.ui.actions.ContextualLaunchAction.isApplicable(ContextualLaunchAction.java:287)
> at org.eclipse.debug.ui.actions.ContextualLaunchAction.fillMenu(ContextualLaunchAction.java:218)
> at org.eclipse.debug.ui.actions.ContextualLaunchAction$1.menuShown(ContextualLaunchAction.java:141)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4245)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313)
> at org.eclipse.jface.action.ActionContributionItem.copyMenu(ActionContributionItem.java:1243)
> at org.eclipse.jface.action.ActionContributionItem.handleShowProxy(ActionContributionItem.java:1223)
> at org.eclipse.jface.action.ActionContributionItem.lambda$7(ActionContributionItem.java:1186)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4245)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1505)
> at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:805)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5761)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:77)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:267)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:4146)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3688)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1118)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1019)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:691)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java: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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
> !SUBENTRY 1 org.eclipse.core.resources 4 372 2016-02-28 10:15:30.039
> !MESSAGE Resource '/AprokectTor' is not open.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21850) Maven project has wrong context root set up after import
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-21850:
----------------------------------
Summary: Maven project has wrong context root set up after import
Key: JBIDE-21850
URL: https://issues.jboss.org/browse/JBIDE-21850
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: easymport
Affects Versions: 4.3.1.CR1
Reporter: Radim Hopp
Importing maven project (in my case "servlet-security" from EAP quickstarts) via easymport has wrong context root (right click on project->Properties->Web Project Settings) configured.
Name of project is servlet-security, but web context root is jboss-servlet-security
This results into 404 when this project gets deployed to server. IDE opens url http://localhost:8080/jboss-servlet-security, but correct url is http://localhost:8080/servlet-security.
Note, that this does not happen when importing this project as existing maven project (not using easymport).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21781) Running Cordova projects with Cordova plugins fails on iOS simulators
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21781?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-21781:
---------------------------------
Fix Version/s: 4.3.1.CR1
> Running Cordova projects with Cordova plugins fails on iOS simulators
> ---------------------------------------------------------------------
>
> Key: JBIDE-21781
> URL: https://issues.jboss.org/browse/JBIDE-21781
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.1.Beta2
> Environment: Mac OS X 10.11.3 (El Capitan);
> XCode 7.2.1;
> JBDS 9.1.0 Beta2
> iPhone 6 Simulator (iOS 9.2) among others
> Reporter: Vineet Reynolds
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Cordova projects with Cordova plugins fail to run correctly when started with the iOS simulator through JBDS.
> This appears to be related to JBIDE-21780 where a default config.xml file is created on the fly in the exported XCode project before the project is built and deployed on the simulator.
> Attaching a JavaScript debugger using Safari indicates that Cordova was not initialized successfully. The following messages are reported:
> {{deviceready has not fired after 5 seconds.}}
> {{Channel not fired: onCordovaInfoReady}}
> which indicates that Cordova failed to initialise.
> As indicated previously, this appears to be related to JBIDE-21780. The config.xml file should be in the location (of the XCode project) as indicated in https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-worki... instead of https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-not-w...
> In the working version, config.xml is at {{demo-ios-working/demo/ios/demo/config.xml}} only whereas in the non-working one, it is at {{demo-ios-not-working/demo/ios/demo/config.xml}} (notice lack of Cordova plugin info) and {{demo-ios-not-working/demo/ios/www/config.xml}}.
> A workaround could be obtained by exporting the project and modifying the config.xml, but that basically renders the JBDS tooling moot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21781) Running Cordova projects with Cordova plugins fails on iOS simulators
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21781?page=com.atlassian.jira.plugi... ]
Gorkem Ercan reassigned JBIDE-21781:
------------------------------------
Assignee: Gorkem Ercan
> Running Cordova projects with Cordova plugins fails on iOS simulators
> ---------------------------------------------------------------------
>
> Key: JBIDE-21781
> URL: https://issues.jboss.org/browse/JBIDE-21781
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.1.Beta2
> Environment: Mac OS X 10.11.3 (El Capitan);
> XCode 7.2.1;
> JBDS 9.1.0 Beta2
> iPhone 6 Simulator (iOS 9.2) among others
> Reporter: Vineet Reynolds
> Assignee: Gorkem Ercan
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Cordova projects with Cordova plugins fail to run correctly when started with the iOS simulator through JBDS.
> This appears to be related to JBIDE-21780 where a default config.xml file is created on the fly in the exported XCode project before the project is built and deployed on the simulator.
> Attaching a JavaScript debugger using Safari indicates that Cordova was not initialized successfully. The following messages are reported:
> {{deviceready has not fired after 5 seconds.}}
> {{Channel not fired: onCordovaInfoReady}}
> which indicates that Cordova failed to initialise.
> As indicated previously, this appears to be related to JBIDE-21780. The config.xml file should be in the location (of the XCode project) as indicated in https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-worki... instead of https://github.com/VineetReynolds/cordova-test/tree/master/demo-ios-not-w...
> In the working version, config.xml is at {{demo-ios-working/demo/ios/demo/config.xml}} only whereas in the non-working one, it is at {{demo-ios-not-working/demo/ios/demo/config.xml}} (notice lack of Cordova plugin info) and {{demo-ios-not-working/demo/ios/www/config.xml}}.
> A workaround could be obtained by exporting the project and modifying the config.xml, but that basically renders the JBDS tooling moot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21780) Cordova projects exported as native projects fails to run in iOS simulator under XCode
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21780?page=com.atlassian.jira.plugi... ]
Gorkem Ercan reassigned JBIDE-21780:
------------------------------------
Assignee: Gorkem Ercan
> Cordova projects exported as native projects fails to run in iOS simulator under XCode
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-21780
> URL: https://issues.jboss.org/browse/JBIDE-21780
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.1.Beta2
> Environment: Mac OS X 10.11.3 (El Capitan);
> XCode 7.2.1;
> JBDS 9.1.0 Beta2
> iPhone 6 Simulator (iOS 9.2) among others
> Reporter: Vineet Reynolds
> Assignee: Gorkem Ercan
> Fix For: 4.3.1.CR1
>
>
> Cordova projects with Cordova plugins when exported as native projects appear to have incorrect locations set for config.xml.
> A new config.xml appears to be created with default content and none of the Cordova plugins in the configuration, which is incorrect. In addition, the original config.xml file is created/copied into the www/ directory, which is ignored by the build and/or runtime.
> When the native project is run in the iOS simulator, it shows errors/warnings that indicate failure in initialising Cordova. Plugins like the Device plugin are not loaded since they cannot be found in the config.xml (assuming the newly created config is overridding the original config), resulting in a failed application start.
> The output window shows the following message:
> {{ERROR: Plugin 'Device' not found, or is not a CDVPlugin. Check your plugin mapping in config.xml.}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21780) Cordova projects exported as native projects fails to run in iOS simulator under XCode
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21780?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-21780:
---------------------------------
Fix Version/s: 4.3.1.CR1
> Cordova projects exported as native projects fails to run in iOS simulator under XCode
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-21780
> URL: https://issues.jboss.org/browse/JBIDE-21780
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.3.1.Beta2
> Environment: Mac OS X 10.11.3 (El Capitan);
> XCode 7.2.1;
> JBDS 9.1.0 Beta2
> iPhone 6 Simulator (iOS 9.2) among others
> Reporter: Vineet Reynolds
> Assignee: Gorkem Ercan
> Fix For: 4.3.1.CR1
>
>
> Cordova projects with Cordova plugins when exported as native projects appear to have incorrect locations set for config.xml.
> A new config.xml appears to be created with default content and none of the Cordova plugins in the configuration, which is incorrect. In addition, the original config.xml file is created/copied into the www/ directory, which is ignored by the build and/or runtime.
> When the native project is run in the iOS simulator, it shows errors/warnings that indicate failure in initialising Cordova. Plugins like the Device plugin are not loaded since they cannot be found in the config.xml (assuming the newly created config is overridding the original config), resulting in a failed application start.
> The output window shows the following message:
> {{ERROR: Plugin 'Device' not found, or is not a CDVPlugin. Check your plugin mapping in config.xml.}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21425) Server adapter wizard: Finish button should be disabled in page which contains connection selection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21425?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21425:
-------------------------------------
Fix Version/s: 4.3.1.CR1
> Server adapter wizard: Finish button should be disabled in page which contains connection selection
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21425
> URL: https://issues.jboss.org/browse/JBIDE-21425
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2, 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> In server adapter wizard on wizard page where selection of a connection is performed, the Finish button is enabled. This should not be possible, because although connection is selected but service, eclipse project and paths are not filled in. Hitting finish button in this stage leads to a new server adapter, which does not do anything and its linked to nothing, because details are empty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years