]
Andre Dietisheim updated JBIDE-13066:
-------------------------------------
Labels: new_and_noteworthy respin-c (was: respin-c)
Assignee: Andre Dietisheim (was: Max Rydahl Andersen)
Release Notes Text:
When you add cartridges to your application we check requirements and conflicts and
suggest you to add or remove further cartridges.
In CR1 we now allow you to ignore these suggestion. You get the full control but may
possibly run into errors if you dont meet the requirements.
Furthermore we now made these checks rely on the cartridge names only and ignore the
versions. This makes sure the tooling wont break when OpenShift upgrades cartridge
versions.
Avoid hard coded cartridge names when embedding cartridges and
handling requirements,conflicts
-----------------------------------------------------------------------------------------------
Key: JBIDE-13066
URL:
https://issues.jboss.org/browse/JBIDE-13066
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.0.0.Beta2
Reporter: Attila Nagy
Assignee: Andre Dietisheim
Priority: Critical
Labels: new_and_noteworthy, respin-c
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: