[jbosstools-issues] [JBoss JIRA] (JBIDE-18306) The obsoleted cartridges are still shown

[ https://issues.jboss.org/browse/JBIDE-18306?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18306: ------------------------------------- Steps to Reproduce: # EXEC: Open OpenShift New Application Wizard: File -> New -> Other... -> OpenShift Application # EXEC: Provide your access credentials # EXEC: Check the cartridge list for *zend-5.6* Result: You can still see the obsolete cartridge *zend-5.6* (standalone-, web-cartridge) !application-wizard-obsolete-cartridge.png! # ASSERT: make sure that you have an application running on OpenShift # EXEC: in OpenShift Explorer: pick "Edit Embeddable Cartridges..." from the context menu of your application # ASSERT: the wizard to edit the embedded cartridges shows up and lists the available cartridges # EXEC: check the list of available cartridges Result: You can still see the obsolete cartridge *metrics-0.1* !edit-embedded-cartridges.png! ps. it's especially important to verify that the tooling still works fine if it doesnt show the obsolete standalone- and embedded cartridges (application- and embedded cartridges wizards). To achieve this have a devenv, ssh to it and do the following: # in ssh: edit /usr/libexec/openshift/cartridges/metrics/metadata/manifest.yml -> Obsolete: false service ruby193-mcollective restart oo-broker oo-admin-ctl-cartridge -c import-node --activate --obsolete # EXEC: in Eclipse: create an application using the mock standalone cartridge and embed the metrics cartridge to it # ASSERT: the application is created and shows up in the Explorer # EXEC: in ssh: edit /usr/libexec/openshift/cartridges/metrics/metadata/manifest.yml -> Obsolete: true service ruby193-mcollective restart oo-broker oo-admin-ctl-cartridge -c import-node --activate --obsolete # EXEC: in ssh: edit /usr/libexec/openshift/cartridges/mock/metadata/manifest.yml -> Obsolete: true service ruby193-mcollective restart oo-broker oo-admin-ctl-cartridge -c import-node --activate --obsolete # EXEC: in Eclipse: the application still shows up in Explorer but: * *mock* cartridge wont show up in the "Basic Cartridges" in application wizard (File->New->OpenShift->New Application) * *metrics* cartridge wont show up in the embed cartridges wizard (Explorer: Edit Embedded Cartridges) was: # EXEC: Open OpenShift New Application Wizard: File -> New -> Other... -> OpenShift Application # EXEC: Provide your access credentials # EXEC: Check the cartridge list for *zend-5.6* Result: You can still see the obsolete cartridge *zend-5.6* (standalone-, web-cartridge) !application-wizard-obsolete-cartridge.png! # ASSERT: make sure that you have an application running on OpenShift # EXEC: in OpenShift Explorer: pick "Edit Embeddable Cartridges..." from the context menu of your application # ASSERT: the wizard to edit the embedded cartridges shows up and lists the available cartridges # EXEC: check the list of available cartridges Result: You can still see the obsolete cartridge *metrics-0.1* !edit-embedded-cartridges.png! ps. it's especially important to verify that the tooling still works fine if it doesnt show the obsolete standalone- and embedded cartridges (application- and embedded cartridges wizards). To achieve this have a devenv, ssh to it and do the following: # in ssh: edit /usr/libexec/openshift/cartridges/metrics/metadata/manifest.yml -> Obsolete: false service ruby193-mcollective restart oo-broker oo-admin-ctl-cartridge -c import-node --activate --obsolete # EXEC: in Eclipse: create an application using the mock standalone cartridge and embed the metrics cartridge to it # ASSERT: the application is created and shows up in the Explorer # EXEC: in ssh: edit /usr/libexec/openshift/cartridges/metrics/metadata/manifest.yml -> Obsolete: true service ruby193-mcollective restart oo-broker oo-admin-ctl-cartridge -c import-node --activate --obsolete # EXEC: in ssh: edit /usr/libexec/openshift/cartridges/mock/metadata/manifest.yml -> Obsolete: true service ruby193-mcollective restart oo-broker oo-admin-ctl-cartridge -c import-node --activate --obsolete -- This message was sent by Atlassian JIRA (v6.3.1#6329)