[jbosstools-issues] [JBoss JIRA] (JBIDE-13866) openshift-java-client: remove hard coded (standalone) cartridges from tests

[Andre Dietisheim (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-13866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-13866:
-------------------------------------

    Description: We currently still have hard coded (standalone) cartridges in our integration tests (not the client code which is not depending on specific cartridges). If we want to have the OpenShift team running our integration test we have to remove those. This is because they may replace existing by new cartridges and therefore can't run our integration tests against new DEVENVs (ex. a dev pinged me and told me he was working on upgrading the php cartridge to a higher version).   (was: We currently still have hard coded (standalone) cartr)

    
> openshift-java-client: remove hard coded (standalone) cartridges from tests
> ---------------------------------------------------------------------------
>
>                 Key: JBIDE-13866
>                 URL: https://issues.jboss.org/browse/JBIDE-13866
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 4.1.0.Alpha2
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>             Fix For: 4.1.x
>
>
> We currently still have hard coded (standalone) cartridges in our integration tests (not the client code which is not depending on specific cartridges). If we want to have the OpenShift team running our integration test we have to remove those. This is because they may replace existing by new cartridges and therefore can't run our integration tests against new DEVENVs (ex. a dev pinged me and told me he was working on upgrading the php cartridge to a higher version). 

--
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