[JBoss JIRA] (JBIDE-21831) Change host to localhost when cdk is selected in new server dialog
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21831?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21831:
---------------------------------------
[~maxandersen], it sounds like an interesting idea. Although I think currently there wouldn't be any use for it.
But here's one argument against it: If you do this and require this field to be set correctly, you will make it harder for users to create their cdk server. Today if you want to create a cdk server adapter, you only need to know the path to your Vagrantfile. With this, you would also need to know the ip that is used.
> Change host to localhost when cdk is selected in new server dialog
> ------------------------------------------------------------------
>
> Key: JBIDE-21831
> URL: https://issues.jboss.org/browse/JBIDE-21831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: new-cdk-server.png
>
>
> When you open the new server dialog, select OpenShift 2, it will set host to openshift.redhat.com. When you then select cdk, it will complain that it only works on localhost. So the suggestion is to make it work the same way OpenShift adapters work and ensure that host is always changed to localhost when you select the cdk adapter.
> This was spotted and brought up by [~mlabuda].
> For reference, this is the JIRA where similar thing was discussed for OpenShift: JBIDE-20114
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21840) Checkbox to save password in Secure Storage is not checked when password is stored
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21840?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-21840.
-------------------------------
Verified on nightly build of JBT with OpenShift plugin build B233.
> Checkbox to save password in Secure Storage is not checked when password is stored
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-21840
> URL: https://issues.jboss.org/browse/JBIDE-21840
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: connection_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: edit-connection-wizard.png, secure-storage.png
>
>
> In OpenShift connection wizard there is a checkbox to store password/token in secure storage. If I choose on an existing OpenShift 3 connection with basic authentication to store password in secure storage, technically it is stored and visible on Secure Storage preference page, but in Connection wizard it is not visible. Upon next opening of the Edit Connection wizard, checkbox is unchecked although password is checked.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21831) Change host to localhost when cdk is selected in new server dialog
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21831?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21831:
---------------------------------------------
please do not think the CDK will not use the host name.
the CDK should know what it is ip/host is - why not have the host name be that value ?
> Change host to localhost when cdk is selected in new server dialog
> ------------------------------------------------------------------
>
> Key: JBIDE-21831
> URL: https://issues.jboss.org/browse/JBIDE-21831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: new-cdk-server.png
>
>
> When you open the new server dialog, select OpenShift 2, it will set host to openshift.redhat.com. When you then select cdk, it will complain that it only works on localhost. So the suggestion is to make it work the same way OpenShift adapters work and ensure that host is always changed to localhost when you select the cdk adapter.
> This was spotted and brought up by [~mlabuda].
> For reference, this is the JIRA where similar thing was discussed for OpenShift: JBIDE-20114
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21895) Resource name collisions after deleting and recreating the application
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-21895:
----------------------------------
Summary: Resource name collisions after deleting and recreating the application
Key: JBIDE-21895
URL: https://issues.jboss.org/browse/JBIDE-21895
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Pavol Srna
Fix For: 4.3.1.CR1
Attachments: Screen Shot 2016-03-17 at 16.19.05.png
1) Create e.g. node application in a openshift project
2) Right click from project explorer -> Delete the application
3) repeat step 1)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21847) Start port forwarding button is disabled after starting and stopping it
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21847?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21847:
---------------------------------------
I tried several times immediately (once the checkbox is enabled) click on the checkbox and StartAll button got enabled.
> Start port forwarding button is disabled after starting and stopping it
> -----------------------------------------------------------------------
>
> Key: JBIDE-21847
> URL: https://issues.jboss.org/browse/JBIDE-21847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: video.ogg-2.ogv
>
>
> In Port Forwarding wizard when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21894) NPE when canceling openshift new app wizard
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-21894:
----------------------------------
Summary: NPE when canceling openshift new app wizard
Key: JBIDE-21894
URL: https://issues.jboss.org/browse/JBIDE-21894
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Pavol Srna
Fix For: 4.3.1.CR1
Attachments: Screen Shot 2016-03-17 at 16.02.08.png, Screen Shot 2016-03-17 at 16.02.20.png
{code}
org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68)
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:4230)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
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:694)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
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)
Caused by: java.lang.NullPointerException
at org.eclipse.jface.databinding.dialog.DialogPageSupport.init(DialogPageSupport.java:184)
at org.eclipse.jface.databinding.dialog.DialogPageSupport.<init>(DialogPageSupport.java:137)
at org.jboss.tools.common.ui.databinding.ParametrizableWizardPageSupport.<init>(ParametrizableWizardPageSupport.java:26)
at org.jboss.tools.common.ui.databinding.ParametrizableWizardPageSupport.create(ParametrizableWizardPageSupport.java:58)
at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateListPage.setupWizardPageSupport(TemplateListPage.java:896)
at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage.createControl(AbstractOpenShiftWizardPage.java:63)
at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
at org.eclipse.jface.window.Window.create(Window.java:430)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
at org.eclipse.jface.window.Window.open(Window.java:792)
at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:279)
at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
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.GeneratedMethodAccessor125.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)
... 40 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21893) Cannot cancel server adapter creation for OS3
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21893?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21893:
-------------------------------------
Fix Version/s: 4.3.1.CR1
> Cannot cancel server adapter creation for OS3
> ---------------------------------------------
>
> Key: JBIDE-21893
> URL: https://issues.jboss.org/browse/JBIDE-21893
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Jan Richter
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.3.1.CR1
>
> Attachments: os3.png
>
>
> Open a clean JBT installation
> -> open servers view, create new server
> -> select OpenShift 3, click next
> -> click cancel or the close cross button
> -> 'Server Error' message pops up, cannot close the wizard
> Workaround: go back to adapter selection and refresh it (i.e. check/uncheck the 'Show downloadable server adapters') - only then can the wizard be closed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21847) Start port forwarding button is disabled after starting and stopping it
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21847?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21847:
-----------------------------------------------
Well, at least it is not a UI issue. 5 seconds wait leaves ports occupied, the process has not released them. It seems strange that the immediate flip of 'Use free ports' on and off works, [~mlabuda], could you please try to flip the checkbox _immediately_ after the message "Stopping ports is requested and eventually will be completed" appears. Could you catch it failing once, too?
Now, I wonder if process to be killed is waiting for the calling thread to finish. [~fbricon], could it be possible? Then, the fix may be starting one more job for polling sockets for a few more seconds.
> Start port forwarding button is disabled after starting and stopping it
> -----------------------------------------------------------------------
>
> Key: JBIDE-21847
> URL: https://issues.jboss.org/browse/JBIDE-21847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: video.ogg-2.ogv
>
>
> In Port Forwarding wizard when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-571) Error loading file switchyard.xml. Unable to load the generated resource.
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-571?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick commented on JBTIS-571:
-----------------------------------------
I thought perhaps that this was a factor with the SwitchYard version of the eclipse project, but that doesn't seem to be the case. I have seen issues opening the editor from the SwitchYard node in the project tree when the project gets corrupted somehow (other things weren't working either, such as the resources directory appearing) but I suspect that's more to do with Eclipse debug workbench weirdness than anything else.
There's still a possibility that a maven build failure in the project itself is lending itself towards the adapter failure, but I really don't know at this point.
> Error loading file switchyard.xml. Unable to load the generated resource.
> -------------------------------------------------------------------------
>
> Key: JBTIS-571
> URL: https://issues.jboss.org/browse/JBTIS-571
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: switchyard
> Affects Versions: 9.0.0.Alpha2
> Reporter: nicolas duminil
> Assignee: Brian Fitzpatrick
> Priority: Blocker
> Fix For: 9.0.0.Beta1
>
> Attachments: jbtis-571_1.png, jbtis-571_2.png, Screencast_JBDS900GA_JBDSISAlpha2.webm
>
>
> After creating a new switchyard project, next time it starts up JBDS is not able to open its own generated siwtchyard.xml file. The error "Error loading file switchyard.xml. Unable to load the generated resource" is displayed. The only choice is the OK button. Pressing it, the JBDS screen doesn't display but JBDS seems to be started and the LCK file created. The only option the user has is to kill the process.
> Tested on Windows 7 and Windows 10 with Java 8.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years