[JBoss JIRA] (JBIDE-13522) Cannot create a connection to OpenShift after fresh install of rhc-tooling
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13522?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13522:
-------------------------------------
Release Notes Text:
Several users could not connect to OpenShift using JBoss Tools anymore. This happened after they installed the latest rhc client tools (1.4.7) for the command line.
We identified the issue in the rhc client tools and enhanced our client library to be able to read the new (express.conf) file format. The rhc tools were fixed in the next release (1.4.8) so that noone should get into these troubles any more.
was:
Several users could not connect to OpenShift using JBoss Tools anymore. This happened after they installed the latest rhc client tools for the command line. We identified an issue in the new rhc client tools and enhanced our client library to be able to read the new (express.conf) file format format.
The rhc tools were also fixed in the next release so that noone should get into these troubles any more.
> Cannot create a connection to OpenShift after fresh install of rhc-tooling
> --------------------------------------------------------------------------
>
> Key: JBIDE-13522
> URL: https://issues.jboss.org/browse/JBIDE-13522
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Environment: linux fedora
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Alpha2
>
>
> The latest rhc tooling is creating an express.conf file with a double quoted *libra_server* entry:
> {code}
> libra_server="openshift.redhat.com"
> {code}
> If you're a new user, install rhc tooling, get the above express.conf and then run JBT, JBT will tell you that your credentials are not valid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-13856) Test jQuery Mobile Palette Wizards on different platforms
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13856?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-13856:
-----------------------------------------------
https://github.com/jbosstools/jbosstools-jst/pull/91
> Test jQuery Mobile Palette Wizards on different platforms
> ---------------------------------------------------------
>
> Key: JBIDE-13856
> URL: https://issues.jboss.org/browse/JBIDE-13856
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jsp/jsf/xml/html source editing
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha2
>
> Attachments: jbide-13856.patch, ubuntu_64_button.png, ubuntu_64_checkboxes.png, ubuntu_64_cjeckbox.png, ubuntu_64_collapsible.png, ubuntu_64_dialog.png, ubuntu_64_footerbar.png, ubuntu_64_grid.png, ubuntu_64_headerbar.png, ubuntu_64_large_font_toggle.png, ubuntu_64_link.png, ubuntu_64_listview.png, ubuntu_64_navbar.png, ubuntu_64_page.png, ubuntu_64_radio.png, ubuntu_64_slider.png, ubuntu_64_textinput.png, ubuntu_64_toggle.png
>
>
> If system font size is set to large, wizard should take it into account.
> For instance:
> !ubuntu_64_large_font_toggle.png!
> Windows 8 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
> jQuery Mobile Palette Widget Wizards work fine.
> Windows 8 64bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
> Wizards do not start
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
> at org.eclipse.swt.SWT.error(SWT.java:4373)
> at org.eclipse.swt.SWT.error(SWT.java:4288)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
> at org.eclipse.swt.SWT.error(SWT.java:4399)
> at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
> at org.eclipse.jface.window.Window.create(Window.java:431)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
> at org.eclipse.jface.window.Window.open(Window.java:790)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
> at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
> Windows 8 32 and 64 bits (Eclipse+Java) Base+JST + Safari:
> jQuery Mobile Palette Widget Wizards work without JavaScript.
> Windows 7 32 and 64 bits (Eclipse+Java) Base+JST + Safari:
> jQuery Mobile Palette Widget Wizards work without JavaScript.
> Windows 7 32 and 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner:
> jQuery Mobile Palette Widget Wizards work fine.
> Windows 7 32bit (Eclipse+Java) Base+JST+VPE+Xulrunner + Safari:
> jQuery Mobile Palette Widget Wizards work fine.
> Windows 7 32 and 64 bits (Eclipse+Java) Base+JST:
> Wizards do not start
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser])
> at org.eclipse.swt.SWT.error(SWT.java:4392)
> at org.eclipse.swt.SWT.error(SWT.java:4307)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4145)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3762)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: org.eclipse.swt.SWTError: No more handles [Safari must be installed to use a SWT.WEBKIT-style Browser]
> at org.eclipse.swt.SWT.error(SWT.java:4418)
> at org.eclipse.swt.browser.WebKit.create(WebKit.java:542)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:99)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizardPage.createControl(AbstractNewHTMLWidgetWizardPage.java:139)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
> at org.eclipse.jface.window.Window.create(Window.java:432)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at org.jboss.tools.common.model.ui.editors.dnd.DropWizardDialog.create(DropWizardDialog.java:95)
> at org.eclipse.jface.window.Window.open(Window.java:791)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
> at org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor$4.run(JSPTextEditor.java:757)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
> MacOs 64 bit (Eclipse+Java) Base+JST+VPE+Xulrunner:
> and
> MacOs 64 bit (Eclipse+Java) Base+JST:
> jQuery Mobile Palette Widget Wizards work fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-13806) OpenShift console does not show the maven build logs anymore
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13806?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13806:
-------------------------------------
Release Notes Text:
The server adapter for OpenShift allows you to publish your local changes to OpenShift. It pops up the console after publishing so that you can have a detailed look at what happened when pushing. In Alpha1 the console was not shown any more. We fixed this for Alpha2.
> OpenShift console does not show the maven build logs anymore
> ------------------------------------------------------------
>
> Key: JBIDE-13806
> URL: https://issues.jboss.org/browse/JBIDE-13806
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha1
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Alpha2
>
>
> The OpenShift tooling does not show the maven build logs after some changes were published on openshift.
> The workaround is to tail log files to see the app server activity (and see when the app is redeployed)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-12724) openshift java client: remove various API elements (show ports etc.)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12724?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12724:
-------------------------------------
Summary: openshift java client: remove various API elements (show ports etc.) (was: openshift java client: remove various API elements (show ports etc.) in protocol 1.1)
> openshift java client: remove various API elements (show ports etc.)
> --------------------------------------------------------------------
>
> Key: JBIDE-12724
> URL: https://issues.jboss.org/browse/JBIDE-12724
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.0.Alpha2
>
>
> upcoming changes for the REST service protocol 1.1 in OpenShift
> {code:title=Mail from Krishan Raman on 09/26/2012}
> I am planning to break 1.0 compatibility for some REST APIs which I think are not in use. Please correct me if this you are aware of some client which uses these APIs.
> /rest/estimates/*
> Estimates API was created for use by UI to calculate estimated number of gears used for a given app descriptor.
> /rest/domains/#{dom_id}/applications/#{app_name}/events # show-port, expose-port, conceal-port
> *port APIs were created for testing Rob's code. Not aware of anyone using them now.
> /rest/domains/#{dom_id}/applications/#{app_name}/gears
> gears API was in use by UI before gear-groups were exposed to get a list of gears in the application. Not aware of anyone using them now.
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-13522) Cannot create a connection to OpenShift after fresh install of rhc-tooling
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13522?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13522:
-------------------------------------
Release Notes Text:
Several users could not connect to OpenShift using JBoss Tools anymore. This happened after they installed the latest rhc client tools for the command line. We identified an issue in the new rhc client tools and enhanced our client library to be able to read the new (express.conf) file format format.
The rhc tools were also fixed in the next release so that noone should get into these troubles any more.
Labels: new_and_noteworthy (was: )
> Cannot create a connection to OpenShift after fresh install of rhc-tooling
> --------------------------------------------------------------------------
>
> Key: JBIDE-13522
> URL: https://issues.jboss.org/browse/JBIDE-13522
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Environment: linux fedora
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Alpha2
>
>
> The latest rhc tooling is creating an express.conf file with a double quoted *libra_server* entry:
> {code}
> libra_server="openshift.redhat.com"
> {code}
> If you're a new user, install rhc tooling, get the above express.conf and then run JBT, JBT will tell you that your credentials are not valid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-13631) URL for embedded cartridges is empty (WATCHER ISSUE)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13631:
-------------------------------------
Description:
Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank
Steps to reproduce:
# ASSERT: make sure you have at least 1 application running
# ASSERT: make sure you have at least 1 cartridge embedded to it, ex. mongo
# EXEC: in OpenShift Explorer: select your embedded cartridge (ex. mongo) and pick *Properties* from the context menu
# EXEC: in the properties view: check *URL* row.
Result:
It's blank, there's no URL shown. This happens to all embedded cartridges currently: mongo, mysql, jenkins, etc.
!no-url.png!
# EXEC: pick *Refresh* from the context menu of the application (in OpenShift Explorer)
# EXEC: switch to properties view and check URL again:
Result:
URL is still blank.
was:Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank
> URL for embedded cartridges is empty (WATCHER ISSUE)
> ----------------------------------------------------
>
> Key: JBIDE-13631
> URL: https://issues.jboss.org/browse/JBIDE-13631
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: existing-application.json, mysql-url-after-creation.png, mysql-url-at-creation.png, mysql-url-listed.png, new-user-creation-dialog.png, new-user-mongo-url-listed.png, new-user-mysql-url-listed.png, no-url.png
>
>
> Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank
> Steps to reproduce:
> # ASSERT: make sure you have at least 1 application running
> # ASSERT: make sure you have at least 1 cartridge embedded to it, ex. mongo
> # EXEC: in OpenShift Explorer: select your embedded cartridge (ex. mongo) and pick *Properties* from the context menu
> # EXEC: in the properties view: check *URL* row.
> Result:
> It's blank, there's no URL shown. This happens to all embedded cartridges currently: mongo, mysql, jenkins, etc.
> !no-url.png!
> # EXEC: pick *Refresh* from the context menu of the application (in OpenShift Explorer)
> # EXEC: switch to properties view and check URL again:
> Result:
> URL is still blank.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-13559) Cannot embed cartridges (WATCHER ISSUE)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13559?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13559:
-------------------------------------
Summary: Cannot embed cartridges (WATCHER ISSUE) (was: Cannot embed cartridges (WATHCER ISSUE))
> Cannot embed cartridges (WATCHER ISSUE)
> ---------------------------------------
>
> Key: JBIDE-13559
> URL: https://issues.jboss.org/browse/JBIDE-13559
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: cannot-remove-apptype.png
>
>
> If you try to embed cartridges (or remove embedded cartridges) in Alpha2 (not released yet), then you wont be able to do it. The Eclipse toolign is complaining that it cannot remove an embeddable cartridge that's actually matching the application type.
> Steps to reproduce
> 1) ASSERT: have some application running on OpenShift (ex. as1 of type jbossas-7)
> 2) ASSERT: double check the the *OpenShift Explorer* is displaying app-type (jbossas-7) as application type behind the application name and as embedded cartridge as child of the application, below the application name)
> 3) EXEC: in the "OpenShift Explorer" pick *Edit Embeddable Cartridges...* from context menu and check some cartridge (ex. switchyard)
> 4) EXEC: hit "Finish"
> Result:
> An error occurrs where the tooling tried to remove an embedded cartridge which matches the application type:
> !cannot-remove-apptype.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (JBIDE-13559) Cannot embed cartridges (WATHCER ISSUE)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13559?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13559:
-------------------------------------
Description:
If you try to embed cartridges (or remove embedded cartridges) in Alpha2 (not released yet), then you wont be able to do it. The Eclipse toolign is complaining that it cannot remove an embeddable cartridge that's actually matching the application type.
Steps to reproduce
1) ASSERT: have some application running on OpenShift (ex. as1 of type jbossas-7)
2) ASSERT: double check the the *OpenShift Explorer* is displaying app-type (jbossas-7) as application type behind the application name and as embedded cartridge as child of the application, below the application name)
3) EXEC: in the "OpenShift Explorer" pick *Edit Embeddable Cartridges...* from context menu and check some cartridge (ex. switchyard)
4) EXEC: hit "Finish"
Result:
An error occurrs where the tooling tried to remove an embedded cartridge which matches the application type:
!cannot-remove-apptype.png!
was:If you try to embed cartridges (or remove embedded cartridges) in Alpha2 (not released yet), then you wont be able to do it. The Eclipse toolign is complaining that it cannot remove an embeddable cartridge that's actually matching the application type.
> Cannot embed cartridges (WATHCER ISSUE)
> ---------------------------------------
>
> Key: JBIDE-13559
> URL: https://issues.jboss.org/browse/JBIDE-13559
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
> Attachments: cannot-remove-apptype.png
>
>
> If you try to embed cartridges (or remove embedded cartridges) in Alpha2 (not released yet), then you wont be able to do it. The Eclipse toolign is complaining that it cannot remove an embeddable cartridge that's actually matching the application type.
> Steps to reproduce
> 1) ASSERT: have some application running on OpenShift (ex. as1 of type jbossas-7)
> 2) ASSERT: double check the the *OpenShift Explorer* is displaying app-type (jbossas-7) as application type behind the application name and as embedded cartridge as child of the application, below the application name)
> 3) EXEC: in the "OpenShift Explorer" pick *Edit Embeddable Cartridges...* from context menu and check some cartridge (ex. switchyard)
> 4) EXEC: hit "Finish"
> Result:
> An error occurrs where the tooling tried to remove an embedded cartridge which matches the application type:
> !cannot-remove-apptype.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months