[
https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-14818:
------------------------------------------
The usecase discussed in the following OpenShift forum post shows that having this page
would pretty much help to ease renaming the war:
https://www.openshift.com/forums/openshift/cannot-publish-a-tomcat-app-to...
We currently have to rename it manually, and we'd have to do this with each change in
the project that should be deployed as "ROOT.war".
there's no "deployments" page for OpenShift that would
allow me to rename a module
----------------------------------------------------------------------------------
Key: JBIDE-14818
URL:
https://issues.jboss.org/browse/JBIDE-14818
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift, server
Affects Versions: 4.1.0.Beta2
Reporter: Andre Dietisheim
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.2.x
In JDF-172 a users tries to deploy an application to OpenShift. He'll use the binary
deployment. In order to have the app showing up at */* he'll want to rename the war to
*ROOT.war*. If he does this in the *Project Explorer* things are fine as long as the
original project is not changed. As soon as there's a change the adapter will
"refresh" the war and re-create it with the project name, it will not update the
ROOT.war. We therefore need a deployments page where the user can rename a deployment.
--
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