[JBoss JIRA] (JBIDE-18368) An internal error occurred during: "Computing connector status".
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18368?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18368:
----------------------------------------
[~jpeterka] I really need more details on how to reproduce this issue.
> An internal error occurred during: "Computing connector status".
> ----------------------------------------------------------------
>
> Key: JBIDE-18368
> URL: https://issues.jboss.org/browse/JBIDE-18368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.CR1b, F20_64
> Reporter: Jiri Peterka
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR2
>
>
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.resolveProfileUnits(ConnectorDescriptorItemUi.java:393)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.access$6(ConnectorDescriptorItemUi.java:390)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:311)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18435) Validation errors in WildFly quickstarts
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-18435:
-------------------------------------
Summary: Validation errors in WildFly quickstarts
Key: JBIDE-18435
URL: https://issues.jboss.org/browse/JBIDE-18435
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: upstream
Affects Versions: 4.2.0.CR1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.2.0.CR2
when importing Wildfly quickstarts, there are some XML files on which some errors are reported by our tooling:
- {{ejb-multi-server/app-one/ejb/src/main/resources/META-INF/jboss-ejb3.xml}}
- {{ejb-multi-server/app-main/web/src/main/webapp/WEB-INF/faces-config.xml}}
- {{cdi-alternative/src/main/webapp/WEB-INF/beans.xml}}
- {{wsat-simple/src/main/webapp/WEB-INF/classes/context-handlers.xml}}
Also, a project had a bad packaging type: jts/application-component-2/pom.xml b/jts/application-component-2/pom.xml ({{jar}} instead of {{ejb}})
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18422) Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
by ZERR Angelo (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18422?page=com.atlassian.jira.plugi... ]
ZERR Angelo commented on JBIDE-18422:
-------------------------------------
I have tried your myApp3 :
* I have import your project in my workspace
* convert to AngularJS project
* open myApp3\www\templates\friend-detail.html
* link starter/FriendDetailCtrl with friend-detail.html
* set the cursor inside the existing {{}} in friend-detail.html
* start completion. None error, and completions shows friend (see attached screenshot).
I cannot help you more, because I cannot reproduce the problem -(
> Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18422
> URL: https://issues.jboss.org/browse/JBIDE-18422
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR2
>
> Attachments: myApp3.zip, Tern completion with friend.png
>
>
> In JBIDE-18273, the JBT/JBDS target platforms were updated to include the latest Tern 0.6.0.201409041810-SNAPSHOT, but the version of AngularJS included in the Early Access site remained at 0.5.0.201408281218. Since these traditionally have been updated IN PARALLEL at the same time, it seems we need a new version of AngularJS in the EA site.
> However, since the latest AngularJS is now 0.6.0.201409231617, maybe we want to pull the latest Tern 0.6.0.201409231610 too, instead of the 2014/09/04 version?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18422) Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
by ZERR Angelo (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18422?page=com.atlassian.jira.plugi... ]
ZERR Angelo updated JBIDE-18422:
--------------------------------
Attachment: Tern completion with friend.png
> Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18422
> URL: https://issues.jboss.org/browse/JBIDE-18422
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR2
>
> Attachments: myApp3.zip, Tern completion with friend.png
>
>
> In JBIDE-18273, the JBT/JBDS target platforms were updated to include the latest Tern 0.6.0.201409041810-SNAPSHOT, but the version of AngularJS included in the Early Access site remained at 0.5.0.201408281218. Since these traditionally have been updated IN PARALLEL at the same time, it seems we need a new version of AngularJS in the EA site.
> However, since the latest AngularJS is now 0.6.0.201409231617, maybe we want to pull the latest Tern 0.6.0.201409231610 too, instead of the 2014/09/04 version?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18306) The obsoleted cartridges are still shown
by Andre Dietisheim (JIRA)
[ 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: restart Eclipse (Eclipse caches the lists of available cartridges)
# 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)
and:
** you can still import the *mock*-cartridge (we obsoleted it in the steps above) application to your workspace
** you still have the *metrics* cartridge listed in the 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
# 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)
and:
** you can still import the *mock*-cartridge (we obsoleted it in the steps above) application to your workspace
** you still have the *metrics* cartridge listed in the embedded cartridges
> The obsoleted cartridges are still shown
> ----------------------------------------
>
> Key: JBIDE-18306
> URL: https://issues.jboss.org/browse/JBIDE-18306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.2.Final
> Reporter: Chunyun Chen
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.CR2
>
> Attachments: application-wizard-obsolete-cartridge.png, edit-embedded-cartridges.png, error-create-obsolete-cartridge.png
>
>
> The obsoleted cartridges are still shown in the cartridge list, like obsoleted cartridge zend-5.6, nodejs-0.6 and metrics-0.1, they should not be shown any more in the list.
> the issue may due to java-client not using the latest 1.7 version restapi.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18306) The obsoleted cartridges are still shown
by Andre Dietisheim (JIRA)
[ 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)
and:
** you can still import the *mock*-cartridge (we obsoleted it in the steps above) application to your workspace
** you still have the *metrics* cartridge listed in the 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
# 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)
> The obsoleted cartridges are still shown
> ----------------------------------------
>
> Key: JBIDE-18306
> URL: https://issues.jboss.org/browse/JBIDE-18306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.2.Final
> Reporter: Chunyun Chen
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.CR2
>
> Attachments: application-wizard-obsolete-cartridge.png, edit-embedded-cartridges.png, error-create-obsolete-cartridge.png
>
>
> The obsoleted cartridges are still shown in the cartridge list, like obsoleted cartridge zend-5.6, nodejs-0.6 and metrics-0.1, they should not be shown any more in the list.
> the issue may due to java-client not using the latest 1.7 version restapi.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18306) The obsoleted cartridges are still shown
by Andre Dietisheim (JIRA)
[ 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
# 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)
> The obsoleted cartridges are still shown
> ----------------------------------------
>
> Key: JBIDE-18306
> URL: https://issues.jboss.org/browse/JBIDE-18306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.2.Final
> Reporter: Chunyun Chen
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.CR2
>
> Attachments: application-wizard-obsolete-cartridge.png, edit-embedded-cartridges.png, error-create-obsolete-cartridge.png
>
>
> The obsoleted cartridges are still shown in the cartridge list, like obsoleted cartridge zend-5.6, nodejs-0.6 and metrics-0.1, they should not be shown any more in the list.
> the issue may due to java-client not using the latest 1.7 version restapi.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18306) The obsoleted cartridges are still shown
by Andre Dietisheim (JIRA)
[ 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
# 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)
> The obsoleted cartridges are still shown
> ----------------------------------------
>
> Key: JBIDE-18306
> URL: https://issues.jboss.org/browse/JBIDE-18306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.2.Final
> Reporter: Chunyun Chen
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.CR2
>
> Attachments: application-wizard-obsolete-cartridge.png, edit-embedded-cartridges.png, error-create-obsolete-cartridge.png
>
>
> The obsoleted cartridges are still shown in the cartridge list, like obsoleted cartridge zend-5.6, nodejs-0.6 and metrics-0.1, they should not be shown any more in the list.
> the issue may due to java-client not using the latest 1.7 version restapi.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months