[JBoss JIRA] (JBIDE-24845) [regression] unable to open the Maven Repositories wizard
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24845?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-24845:
-------------------------------------
Sprint: devex #139 October 2017
> [regression] unable to open the Maven Repositories wizard
> ---------------------------------------------------------
>
> Key: JBIDE-24845
> URL: https://issues.jboss.org/browse/JBIDE-24845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.4.4.Final
> Reporter: Fred Bricon
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.1.Final
>
>
> 1 - open Preferences > JBoss Tools > JBoss Maven Integration
> 2 - click on the Configure Maven Repositories... button
> expected: the Maven repositories wizard open
> actual: Unhandled event loop exception:
> {noformat}
> java.lang.NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE
> at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.getUserSettings(ConfigureMavenRepositoriesWizardPage.java:988)
> at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.createControl(ConfigureMavenRepositoriesWizardPage.java:242)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:176)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:688)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:580)
> at org.eclipse.jface.window.Window.create(Window.java:426)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.jboss.tools.maven.ui.preferences.ConfiguratorPreferencePage$2.widgetSelected(ConfiguratorPreferencePage.java:155)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4257)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4081)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211)
> at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:59)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24979) Scale up/down/to: NPE if you have only a rc, no dc for your app
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24979?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24979:
-------------------------------
Sprint: devex #139 October 2017 (was: devex #138 September 2017)
> Scale up/down/to: NPE if you have only a rc, no dc for your app
> ---------------------------------------------------------------
>
> Key: JBIDE-24979
> URL: https://issues.jboss.org/browse/JBIDE-24979
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.x
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Labels: openshift_v3, scale
> Fix For: 4.5.x
>
> Attachments: eap-without-service-nor-deploymentconfig.json, image-2017-09-04-21-24-57-027.png
>
>
> # ASSERT: make sure that you have an app that has *NO* deployment config, just a replication controller
> (EXEC: if you dont, create it via the attached custom template [^eap-without-service-nor-deploymentconfig.json])
> # EXEC: in OpenShift explorer: select the pod for your rc, pick "Scale > Up" or "Scale > Down" or "Scale > To"
> !image-2017-09-04-21-24-57-027.png!
> The very same is true if you do the same via the properties view "Deployments". There's a "Scale" item for the deployment context menu, but it does nothing.
> Result:
> Nothing happens and in the log you discover the following:
> {code}
> org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
> 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:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:431)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:446)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:472)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4257)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1502)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1525)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1510)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1314)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4081)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> 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:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:143)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:136)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.getDeploymentConfig(ScaleDeploymentHandler.java:106)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler.execute(ScaleDeploymentHandler.java:78)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
> at sun.reflect.GeneratedMethodAccessor104.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25093) IT: create tests for the Docker discovery feature
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25093?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25093:
----------------------------------
Story Points: 13 (was: 8)
> IT: create tests for the Docker discovery feature
> -------------------------------------------------
>
> Key: JBIDE-25093
> URL: https://issues.jboss.org/browse/JBIDE-25093
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Ondrej Dockal
> Labels: cdk, integration-test, openshift_v3
> Fix For: 4.5.x
>
> Attachments: image-2017-09-22-17-35-34-902.png
>
>
> in JBIDE-24491 we introduced the ability to look up the docker registry in the cdk:
> !image-2017-09-22-17-35-34-902.png!
> We should also test that the docker registry in the connection is updated when the cdk starts up (see JBIDE-25046).
> We should now also have this covered by bot-tests. Especially the bugs found in JBIDE-25046 and JBIDE-25049 should be covered.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25093) IT: create tests for the Docker discovery feature
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25093?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-25093 at 10/11/17 8:46 AM:
-----------------------------------------------------------------
Same start for all test cases:
0. EXEC: CDK 3 Server adapter is created, state is Stopped.
Base case:
1. EXEC: CDK 3 adapter is started, OS 3 connection created and OS 3 edit connection wizard is opened. Advanced section is shown up.
2. EXEC: Clicking discover button fills up the Image Registry URL label with value
3. ASSERT: The filled up value is the same as output from calling 'minishift openshift registry' (can be done via Java process?)
Registy URL not found case (JBIDE-25049):
1. EXEC: Start CDK 3 server adapter, OS 3 connection is created
2. EXEC: Remove CDK 3 Adapter without stopping it
3. EXEC: Add new CDK 3 server adapter that is in state Stopped (but minishift is runnig)
4. EXEC: Have OS 3 edit connection wizard opened. Advanced section is shown up.
5. EXEC: Click the Discovery button
6. ASSERT: Registry URL not found dialog is active, proper message is at place
Another case 1:
Check the image registry url is updated for more OS 3 connections than one when CDK 3 server adapter is started (JBIDE-25120, JBIDE-25121) and button Discovery fills up the url of image registry url.
Another case 2:
Check warning if image registry url would be overwritten by clicking the Discover button. Do not know, how to reproduce (JBIDE-25014)
was (Author: odockal):
Same start for all test cases:
0. EXEC: CDK 3 Server adapter is created, state is Stopped.
Base case:
1. EXEC: CDK 3 adapter is started, OS 3 connection created and OS 3 edit connection wizard is opened. Advanced section is shown up.
2. EXEC: Clicking discover button fills up the Image Registry URL label with value
3. ASSERT: The filled up value is the same as output from calling 'minishift openshift registry' (can be done via Java process?)
Registy URL not found case (https://issues.jboss.org/browse/JBIDE-25049):
1. EXEC: Start CDK 3 server adapter, OS 3 connection is created
2. EXEC: Remove CDK 3 Adapter without stopping it
3. EXEC: Add new CDK 3 server adapter that is in state Stopped (but minishift is runnig)
4. EXEC: Have OS 3 edit connection wizard opened. Advanced section is shown up.
5. EXEC: Click the Discovery button
6. ASSERT: Registry URL not found dialog is active, proper message is at place
Another case 1:
Check the image registry url is updated for more OS 3 connections than one when CDK 3 server adapter is started (https://issues.jboss.org/browse/JBIDE-25120, https://issues.jboss.org/browse/JBIDE-25121) and button Discovery fills up the url of image registry url.
Another case 2:
Check warning if image registry url would be overwritten by clicking the Discover button. Do not know, how to reproduce (https://issues.jboss.org/browse/JBIDE-25014)
> IT: create tests for the Docker discovery feature
> -------------------------------------------------
>
> Key: JBIDE-25093
> URL: https://issues.jboss.org/browse/JBIDE-25093
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Ondrej Dockal
> Labels: cdk, integration-test, openshift_v3
> Fix For: 4.5.x
>
> Attachments: image-2017-09-22-17-35-34-902.png
>
>
> in JBIDE-24491 we introduced the ability to look up the docker registry in the cdk:
> !image-2017-09-22-17-35-34-902.png!
> We should also test that the docker registry in the connection is updated when the cdk starts up (see JBIDE-25046).
> We should now also have this covered by bot-tests. Especially the bugs found in JBIDE-25046 and JBIDE-25049 should be covered.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25093) IT: create tests for the Docker discovery feature
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25093?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-25093 at 10/11/17 8:46 AM:
-----------------------------------------------------------------
Same start for all test cases:
0. EXEC: CDK 3 Server adapter is created, state is Stopped.
Base case:
1. EXEC: CDK 3 adapter is started, OS 3 connection created and OS 3 edit connection wizard is opened. Advanced section is shown up.
2. EXEC: Clicking discover button fills up the Image Registry URL label with value
3. ASSERT: The filled up value is the same as output from calling 'minishift openshift registry' (can be done via Java process?)
Registy URL not found case (https://issues.jboss.org/browse/JBIDE-25049):
1. EXEC: Start CDK 3 server adapter, OS 3 connection is created
2. EXEC: Remove CDK 3 Adapter without stopping it
3. EXEC: Add new CDK 3 server adapter that is in state Stopped (but minishift is runnig)
4. EXEC: Have OS 3 edit connection wizard opened. Advanced section is shown up.
5. EXEC: Click the Discovery button
6. ASSERT: Registry URL not found dialog is active, proper message is at place
Another case 1:
Check the image registry url is updated for more OS 3 connections than one when CDK 3 server adapter is started (https://issues.jboss.org/browse/JBIDE-25120, https://issues.jboss.org/browse/JBIDE-25121) and button Discovery fills up the url of image registry url.
Another case 2:
Check warning if image registry url would be overwritten by clicking the Discover button. Do not know, how to reproduce (https://issues.jboss.org/browse/JBIDE-25014)
was (Author: odockal):
Same start for all test cases:
0. EXEC: CDK 3 Server adapter is created, state is Stopped.
Base case:
1. EXEC: CDK 3 adapter is started, OS 3 connection created and OS 3 edit connection wizard is opened. Advanced section is shown up.
2. EXEC: Clicking discover button fills up the Image Registry URL label with value
3. ASSERT: The filled up value is the same as output from calling 'minishift openshift registry' (can be done via Java process?)
Registy URL not found case (JBIDE-25049):
1. EXEC: Start CDK 3 server adapter, OS 3 connection is created
2. EXEC: Remove CDK 3 Adapter without stopping it
3. EXEC: Add new CDK 3 server adapter that is in state Stopped (but minishift is runnig)
4. EXEC: Have OS 3 edit connection wizard opened. Advanced section is shown up.
5. EXEC: Click the Discovery button
6. ASSERT: Registry URL not found dialog is active, proper message is at place
Check the image registry url is updated for more OS 3 connections than one when CDK 3 server adapter is started (JBIDE-25120, JBIDE-25121) and button Discovery fills up the url of image registry url.
> IT: create tests for the Docker discovery feature
> -------------------------------------------------
>
> Key: JBIDE-25093
> URL: https://issues.jboss.org/browse/JBIDE-25093
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Ondrej Dockal
> Labels: cdk, integration-test, openshift_v3
> Fix For: 4.5.x
>
> Attachments: image-2017-09-22-17-35-34-902.png
>
>
> in JBIDE-24491 we introduced the ability to look up the docker registry in the cdk:
> !image-2017-09-22-17-35-34-902.png!
> We should also test that the docker registry in the connection is updated when the cdk starts up (see JBIDE-25046).
> We should now also have this covered by bot-tests. Especially the bugs found in JBIDE-25046 and JBIDE-25049 should be covered.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25093) IT: create tests for the Docker discovery feature
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25093?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-25093 at 10/11/17 8:43 AM:
-----------------------------------------------------------------
Same start for all test cases:
0. EXEC: CDK 3 Server adapter is created, state is Stopped.
Base case:
1. EXEC: CDK 3 adapter is started, OS 3 connection created and OS 3 edit connection wizard is opened. Advanced section is shown up.
2. EXEC: Clicking discover button fills up the Image Registry URL label with value
3. ASSERT: The filled up value is the same as output from calling 'minishift openshift registry' (can be done via Java process?)
Registy URL not found case (JBIDE-25049):
1. EXEC: Start CDK 3 server adapter, OS 3 connection is created
2. EXEC: Remove CDK 3 Adapter without stopping it
3. EXEC: Add new CDK 3 server adapter that is in state Stopped (but minishift is runnig)
4. EXEC: Have OS 3 edit connection wizard opened. Advanced section is shown up.
5. EXEC: Click the Discovery button
6. ASSERT: Registry URL not found dialog is active, proper message is at place
Check the image registry url is updated for more OS 3 connections than one when CDK 3 server adapter is started (JBIDE-25120, JBIDE-25121) and button Discovery fills up the url of image registry url.
was (Author: odockal):
Same start for all test cases:
0. EXEC: CDK 3 Server adapter is created, state is Stopped.
Base case:
1. EXEC: CDK 3 adapter is started, OS 3 connection created and OS 3 edit connection wizard is opened. Advanced section is shown up.
2. EXEC: Clicking discover button fills up the Image Registry URL label with value
3. ASSERT: The filled up value is the same as output from calling 'minishift openshift registry' (can be done via Java process?)
Registy URL not found case (JBIDE-25049):
1. EXEC: Start CDK 3 server adapter, OS 3 connection is created
2. EXEC: Remove CDK 3 Adapter without stopping it
3. EXEC: Add new CDK 3 server adapter that is in state Stopped (but minishift is runnig)
4. EXEC: Have OS 3 edit connection wizard opened. Advanced section is shown up.
5. EXEC: Click the Discovery button
6. ASSERT: Registry URL not found dialog is active, proper message is at place
> IT: create tests for the Docker discovery feature
> -------------------------------------------------
>
> Key: JBIDE-25093
> URL: https://issues.jboss.org/browse/JBIDE-25093
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Ondrej Dockal
> Labels: cdk, integration-test, openshift_v3
> Fix For: 4.5.x
>
> Attachments: image-2017-09-22-17-35-34-902.png
>
>
> in JBIDE-24491 we introduced the ability to look up the docker registry in the cdk:
> !image-2017-09-22-17-35-34-902.png!
> We should also test that the docker registry in the connection is updated when the cdk starts up (see JBIDE-25046).
> We should now also have this covered by bot-tests. Especially the bugs found in JBIDE-25046 and JBIDE-25049 should be covered.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 6 months