[
https://issues.jboss.org/browse/JBIDE-13066?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-13066:
------------------------------------------
I basically agree on the complain about the hard-coded cartridge names. We get the
available cartridges from OpenShift when you're up to embed a cartridge (when
create/importing an application or embedding/removing cartridges from an application).
These cartridges are not hard-coded, they're retrieved from the service.
On the other hand, when dealing with dependencies we are hard-coding. There's
currently no other way for us to achieve this since there's no metadata yet, that
would inform us about dependencies and conflicts. As soon as OpenShift offers that
metadata we'll be able to get over to dynamic cartridge dependencies and conflicts and
get rid of the hard-coded ones we currently have.
Hard-coded cartridge name 'mongodb-2.0' in OpenShift Plugin
-----------------------------------------------------------
Key: JBIDE-13066
URL:
https://issues.jboss.org/browse/JBIDE-13066
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Attila Nagy
Assignee: Andre Dietisheim
Fix For: 4.0.0.CR1
The MongoDB version supported by OpenShift has been recently changed. Now it support
MongoDB 2.2.
In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse
warns me that 'mongodb-2.0' is a dependency.
Additionally I'm unable to embed those cartridges. I can see the following error
message.
Could not embed cartridges for application myphptesting
Could not request
https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...:
Operation failed on parameter "cartridge", sevirty "ERROR" with exit
code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2,
switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1,
phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.4)"
--
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