[
https://issues.jboss.org/browse/JBIDE-11288?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-11288:
-------------------------------------
Priority: Minor (was: Critical)
downgraded since the wizard currently errors correctly, the behaviour is simply annoying
and could be avoided with proper validation. Even though as soon as new reserved names
appear on the PaaS we'd still have the very same annoying behaviour back again.
Investigate name exceptions of OpenShift Application
----------------------------------------------------
Key: JBIDE-11288
URL:
https://issues.jboss.org/browse/JBIDE-11288
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Stefan Bunciak
Assignee: Andre Dietisheim
Priority: Minor
Fix For: 3.3.0.Beta3
We should find out which names can be used as OpenShift Application name.
I've encountered a problem trying to create aplication called
"*richfaces*":
Could not create application "richfaces": The supplied application name
'richfaces' is not allowed
Could not configure application "richfaces" at
"https://openshift.redhat.com/broker/cartridge"
After investigating all "naming exceptions" we should add some validation to
the OpenShift wizard.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira