[ https://issues.jboss.org/browse/JBIDE-18306?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18306: ------------------------------------------ we cannot move to protocol 1.7 that's for sure. But protocol 1.2 is perfectly able to know about obsolte cartridges, there's a property "obsolete" in the json: OSJC-110. The rhc tooling is talking protocol 1.7 anyhow and thus doesnt report obsolete cartridges: {code} jbossas-7 JBoss Application Server 7 web jboss-dv-6.0.0 (!) JBoss Data Virtualization 6 web jbosseap-6 (*) JBoss Enterprise Application Platform 6 web jenkins-1 Jenkins Server web nodejs-0.10 Node.js 0.10 web perl-5.10 Perl 5.10 web php-5.3 PHP 5.3 web php-5.4 PHP 5.4 web zend-6.1 PHP 5.4 with Zend Server 6.1 web python-2.6 Python 2.6 web python-2.7 Python 2.7 web python-3.3 Python 3.3 web ruby-1.8 Ruby 1.8 web ruby-1.9 Ruby 1.9 web ruby-2.0 Ruby 2.0 web jbossews-1.0 Tomcat 6 (JBoss EWS 1.0) web jbossews-2.0 Tomcat 7 (JBoss EWS 2.0) web jboss-vertx-2.1 (!) Vert.x 2.1 web diy-0.1 Do-It-Yourself 0.1 web 10gen-mms-agent-0.1 10gen Mongo Monitoring Service Agent addon cron-1.4 Cron 1.4 addon jenkins-client-1 Jenkins Client addon mongodb-2.4 MongoDB 2.4 addon mysql-5.1 MySQL 5.1 addon mysql-5.5 MySQL 5.5 addon phpmyadmin-4 phpMyAdmin 4.0 addon postgresql-8.4 PostgreSQL 8.4 addon postgresql-9.2 PostgreSQL 9.2 addon rockmongo-1.1 RockMongo 1.1 addon switchyard-0 SwitchYard 0.8.0 addon haproxy-1.4 Web Load Balancer addon {code} I was mistaken by a mail in april where the OpenShift dev team said that they would filter the deprecated cartridges out. Apparently the intent was to filter them out in protocol 1.7 only, leaving the prior ones alone. -- This message was sent by Atlassian JIRA (v6.3.1#6329)