[jbosstools-issues] [JBoss JIRA] (JBIDE-13066) Avoid hard coded cartridge names when embedding cartridges and handling requirements, conflicts

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738940#comment-12738940 ] 

Andre Dietisheim edited comment on JBIDE-13066 at 12/3/12 10:11 AM:
--------------------------------------------------------------------

this was closed by mistake, reopening.

                
      was (Author: adietish):
    this was closed by mistake

                  
> 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
>             Fix For: 4.1.x, 4.0.x
>
>
> 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/myphptesting/cartridges: 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