[
https://issues.jboss.org/browse/JBIDE-15054?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-15054:
-------------------------------------
Steps to Reproduce:
# EXEC: launch OpenShift application wizard
# EXEC: choose some name and some application type (ex. jbossas-7)
# EXEC: in the embedded cartridges, choose
* rockmongo
* mongodb
* phpmyadmin
* mysql
* EXEC: hit Finish
Result:
After some processing, the wizards becomes all enabled again, no error is visible even
though it's clear that the was a problem. In the EClipse log you spot:
{code}
!ENTRY org.jboss.tools.common.ui 4 0 2013-06-28 10:02:59.789
!MESSAGE The operation 'Adding/removing cartridges for application
"tescht"...' was cancelled
{code}
The application was created and the cartridges were imported though. Sp it was the wizard
that cancelled the job since it looked to him as it took too much time.
was:
# EXEC: launch OpenShift application wizard
# EXEC: choose some name and some application type (ex. jbossas-7)
# EXEC: in the embedded cartridges, choose
* rockmongo
* mongodb
* phpmyadmin
* mysql
* EXEC: hit Finish
Result:
After some processing, the wizards becomes all enabled again, no error is visible even
though it's clear that the was a problem. In the EClipse log you spot:
{code}
{code}
!ENTRY org.jboss.tools.common.ui 4 0 2013-06-28 10:02:59.789
!MESSAGE The operation 'Adding/removing cartridges for application
"tescht"...' was cancelled
{code}
{code}
The application was created and the cartridges were imported though. Sp it was the wizard
that cancelled the job since it looked to him as it took too much time.
embed cartridges: cannot embed rockmongo + mongo + phpmyadmin + mysql
at the same time
--------------------------------------------------------------------------------------
Key: JBIDE-15054
URL:
https://issues.jboss.org/browse/JBIDE-15054
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.2.x
--
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