[JBoss JIRA] (JBIDE-25838) Explorer: expand connection to the level that it was expanded to after editing it
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25838?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-25838:
----------------------------------------
Assignee: Dmitrii Bocharov
> Explorer: expand connection to the level that it was expanded to after editing it
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-25838
> URL: https://issues.jboss.org/browse/JBIDE-25838
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: connection, explorer
> Fix For: 4.5.3.Final
>
>
> steps:
> # ASSERT: in OpenShift Explorer: have a connection that is expanded to at least show a/all the projects
> # EXEC: edit the connection, change the url, hit "Finish"
> Result:
> Connection is updated (refreshed) but collapsed, wont show the/all the projects
> Expected result:
> Connection is updated (refreshed) and expanded like it was before editing it, showing the project(s) (and even service(s) if it was expanded to that level before editing it)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25829) Error when you cancel minishift location selection while creating cdk server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25829?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-25829.
---------------------------------
Resolution: Done
* 306942a - JBIDE-25829 - simple NPE (3 hours ago) <Rob Stryker>
> Error when you cancel minishift location selection while creating cdk server
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25829
> URL: https://issues.jboss.org/browse/JBIDE-25829
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.3.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM3
>
>
> I just noticed there is an error when you start the New Server dialog, select cdk 3.2+ and on the next page you first try to Browse for the minishift binary and then you change your mind and cancel that window.
> {code}
> Unhandled event loop exception
> java.lang.NullPointerException
> at java.io.File.<init>(File.java:277)
> at org.jboss.tools.openshift.cdk.server.ui.internal.CDK3ServerWizardFragment.kickValidationJob(CDK3ServerWizardFragment.java:218)
> at org.jboss.tools.openshift.cdk.server.ui.internal.CDK3ServerWizardFragment.access$3(CDK3ServerWizardFragment.java:214)
> at org.jboss.tools.openshift.cdk.server.ui.internal.CDK3ServerWizardFragment$3.widgetSelected(CDK3ServerWizardFragment.java:197)
> 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:4258)
> 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:4082)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3699)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:58)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4258)
> 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:4082)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3699)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
> 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)
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25832) Credentials composite doesn't update if underlying model changes
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25832?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-25832:
--------------------------------
Fix Version/s: 4.5.3.AM3
> Credentials composite doesn't update if underlying model changes
> ----------------------------------------------------------------
>
> Key: JBIDE-25832
> URL: https://issues.jboss.org/browse/JBIDE-25832
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: foundation, runtime-detection
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM3
>
>
> Credentials composite doesn't update if underlying model changes. Workflow for this is a bit complicated, but:
> 1) Start with a clean workspace
> 2) Open server view
> 3) Choose cdk 3.2+
> 4) Click "Download runtime..." (DO NOT add credentials before this!)
> 5) In the download runtime dialog, add the proper credentials
> 6) Complete the dl-rt wizard
> 7) Note the new server wizard is downloading the runtime and all widgets are frozen
> 8) The download completes, some fields get filled in
> 9) The credential combo does not get updated. They are disabled except for 'add'
> 10) If you try to add the same credentials again, it will tell you they already exist
> 11) You must cancel the wizard and start it over.
> Also as part of this patch, we should change all dl-rt strings that reference jboss.org credentials, as they have been replaced with redhat.com credentials.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25832) Credentials composite doesn't update if underlying model changes
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25832?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-25832:
-----------------------------------
Assignee: Rob Stryker
> Credentials composite doesn't update if underlying model changes
> ----------------------------------------------------------------
>
> Key: JBIDE-25832
> URL: https://issues.jboss.org/browse/JBIDE-25832
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: foundation, runtime-detection
> Reporter: Rob Stryker
> Assignee: Rob Stryker
>
> Credentials composite doesn't update if underlying model changes. Workflow for this is a bit complicated, but:
> 1) Start with a clean workspace
> 2) Open server view
> 3) Choose cdk 3.2+
> 4) Click "Download runtime..." (DO NOT add credentials before this!)
> 5) In the download runtime dialog, add the proper credentials
> 6) Complete the dl-rt wizard
> 7) Note the new server wizard is downloading the runtime and all widgets are frozen
> 8) The download completes, some fields get filled in
> 9) The credential combo does not get updated. They are disabled except for 'add'
> 10) If you try to add the same credentials again, it will tell you they already exist
> 11) You must cancel the wizard and start it over.
> Also as part of this patch, we should change all dl-rt strings that reference jboss.org credentials, as they have been replaced with redhat.com credentials.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25736) deprecate features from JBoss Tools with low usage / low development
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25736?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25736:
------------------------------------
I've updated the components pages for JBIDE and JBDS jira to add "Deprecated" or "Removed" to the component descriptions:
https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.j...
https://issues.jboss.org/projects/JBDS?selectedItem=com.atlassian.jira.ji...
Also commented out a number of array entries from here so we do less JIRA and N&N manipulation for steady-state/deprecated/removed components:
https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/compon...
> deprecate features from JBoss Tools with low usage / low development
> --------------------------------------------------------------------
>
> Key: JBIDE-25736
> URL: https://issues.jboss.org/browse/JBIDE-25736
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim, build, cdi, forge, jsf, livereload, portal-gatein, seam2, webservices
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM3
>
> Attachments: Screenshot 2018-03-02 14.51.03.png
>
>
> This issue is to consider *deprecating* the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked.
> * jbosstools-portlet
> * jbosstools-aerogear
> * jbosstools-browsersim
> * jbosstools-livereload
> * {color:red}-jbosstools-webservices-{color}
> * {color:red}-jbosstools-javaee-{color}
> * {color:red}-jbosstools-forge-{color}
> These projects could be *removed*, since they were deprecated some time ago:
> * jbosstools-freemarker
> * jbosstools-arquillian
> For supporting arguments, see this doc (RH only, sorry):
> https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25832) Credentials composite doesn't update if underlying model changes
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25832?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25832:
-------------------------------
Sprint: devex #146 March 2018
> Credentials composite doesn't update if underlying model changes
> ----------------------------------------------------------------
>
> Key: JBIDE-25832
> URL: https://issues.jboss.org/browse/JBIDE-25832
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: foundation, runtime-detection
> Reporter: Rob Stryker
>
> Credentials composite doesn't update if underlying model changes. Workflow for this is a bit complicated, but:
> 1) Start with a clean workspace
> 2) Open server view
> 3) Choose cdk 3.2+
> 4) Click "Download runtime..." (DO NOT add credentials before this!)
> 5) In the download runtime dialog, add the proper credentials
> 6) Complete the dl-rt wizard
> 7) Note the new server wizard is downloading the runtime and all widgets are frozen
> 8) The download completes, some fields get filled in
> 9) The credential combo does not get updated. They are disabled except for 'add'
> 10) If you try to add the same credentials again, it will tell you they already exist
> 11) You must cancel the wizard and start it over.
> Also as part of this patch, we should change all dl-rt strings that reference jboss.org credentials, as they have been replaced with redhat.com credentials.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25837) CDK detected again after devstudio restart
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25837?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-25837:
---------------------------------------
Update: I noticed that cdk is not detected as new again as I previously thought - the dialog will correctly say that it's already there. So the JIRA title is a bit misleading now, but I'm not sure how better to call it. It's still a bug in my opinion - the dialog should not be displayed at all.
I can reproduce this again and again by restarting the IDE. Also, even if I select "Hide already created runtimes", click OK and restart the IDE, it will appear again and the checkbox is unselected again.
> CDK detected again after devstudio restart
> ------------------------------------------
>
> Key: JBIDE-25837
> URL: https://issues.jboss.org/browse/JBIDE-25837
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, runtime-detection
> Affects Versions: 4.5.3.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Attachments: cdk-repetitive-detection.png
>
>
> This is basically why I saw JBIDE-25836 in the first place (Windows overlapping when selecting a quick fix in runtime detection dialog).
> I had an installation of devstudio and as usual, cdk server adapter was automatically there. That's expected - when I install devstudio and start it, runtime detection will notice ~/.minishift exists and will quietly create a server adapter with minishift binary location missing.
> Then I installed updates and restarted the IDE. On the next start, I was shown the runtime detection dialog - it showed cdk (based on existing ~/.minishift) and it show an error that minishift binary is missing. This seems to be a bug - there was no new server found, only the existing cdk adapter.
> !cdk-repetitive-detection.png!
> I checked again on a clean installation and was able to reproduce easily - a simple IDE restart will do. See the steps to reproduce.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25837) CDK detected again after devstudio restart
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25837?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-25837:
----------------------------------
Description:
This is basically why I saw JBIDE-25836 in the first place (Windows overlapping when selecting a quick fix in runtime detection dialog).
I had an installation of devstudio and as usual, cdk server adapter was automatically there. That's expected - when I install devstudio and start it, runtime detection will notice ~/.minishift exists and will quietly create a server adapter with minishift binary location missing.
Then I installed updates and restarted the IDE. On the next start, I was shown the runtime detection dialog - it showed cdk (based on existing ~/.minishift) and it show an error that minishift binary is missing. This seems to be a bug - there was no new server found, only the existing cdk adapter.
!cdk-repetitive-detection.png!
I checked again on a clean installation and was able to reproduce easily - a simple IDE restart will do. See the steps to reproduce.
was:
This is basically why I saw JBIDE-25836 in the first place (Windows overlapping when selecting a quick fix in runtime detection dialog).
I had an installation of devstudio and as usual, cdk server adapter was automatically there. That's expected - when I install devstudio and start it, runtime detection will notice ~/.minishift exists and will quietly create a server adapter with minishift binary location missing.
Then I installed updates and restarted the IDE. On the next start, I was shown the runtime detection dialog - it found cdk (based on existing ~/.minishift) and it show an error that minishift binary is missing. This seems to be a bug - the cdk server adapter was already there.
!cdk-repetitive-detection.png!
I checked again on a clean installation and was able to reproduce easily - a simple IDE restart will do. See the steps to reproduce.
> CDK detected again after devstudio restart
> ------------------------------------------
>
> Key: JBIDE-25837
> URL: https://issues.jboss.org/browse/JBIDE-25837
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, runtime-detection
> Affects Versions: 4.5.3.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Attachments: cdk-repetitive-detection.png
>
>
> This is basically why I saw JBIDE-25836 in the first place (Windows overlapping when selecting a quick fix in runtime detection dialog).
> I had an installation of devstudio and as usual, cdk server adapter was automatically there. That's expected - when I install devstudio and start it, runtime detection will notice ~/.minishift exists and will quietly create a server adapter with minishift binary location missing.
> Then I installed updates and restarted the IDE. On the next start, I was shown the runtime detection dialog - it showed cdk (based on existing ~/.minishift) and it show an error that minishift binary is missing. This seems to be a bug - there was no new server found, only the existing cdk adapter.
> !cdk-repetitive-detection.png!
> I checked again on a clean installation and was able to reproduce easily - a simple IDE restart will do. See the steps to reproduce.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25837) CDK detected again after devstudio restart
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25837?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-25837:
----------------------------------
Steps to Reproduce:
0. Make sure you have something in ~/.minishift so that runtime detection will create a cdk server adapter automatically
1. Install devstudio and start it with a brand new workspace
2. Check that cdk server adapter was created automatically after the startup, minishift binary is missing - all good, don't do anything
3. Restart the IDE
4. Upon startup, the runtime detection dialog will pop up, only showing already installed cdk, no new runtime - this is a bug
was:
0. Make sure you have something in ~/.minishift so that runtime detection will create a cdk server adapter automatically
1. Install devstudio and start it with a brand new workspace
2. Check that cdk server adapter was created automatically after the startup, minishift binary is missing - all good, don't do anything
3. Restart the IDE
4. Upon startup, the runtime detection dialog will pop up, detecting cdk - this is a bug
> CDK detected again after devstudio restart
> ------------------------------------------
>
> Key: JBIDE-25837
> URL: https://issues.jboss.org/browse/JBIDE-25837
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, runtime-detection
> Affects Versions: 4.5.3.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Attachments: cdk-repetitive-detection.png
>
>
> This is basically why I saw JBIDE-25836 in the first place (Windows overlapping when selecting a quick fix in runtime detection dialog).
> I had an installation of devstudio and as usual, cdk server adapter was automatically there. That's expected - when I install devstudio and start it, runtime detection will notice ~/.minishift exists and will quietly create a server adapter with minishift binary location missing.
> Then I installed updates and restarted the IDE. On the next start, I was shown the runtime detection dialog - it found cdk (based on existing ~/.minishift) and it show an error that minishift binary is missing. This seems to be a bug - the cdk server adapter was already there.
> !cdk-repetitive-detection.png!
> I checked again on a clean installation and was able to reproduce easily - a simple IDE restart will do. See the steps to reproduce.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months