[
https://issues.jboss.org/browse/JBIDE-14818?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-14818 at 11/26/13 10:02 AM:
---------------------------------------------------------------------
i merged this locally and this works fine for adapters that I create via Server adapter
wizard. Those dont have the "magic project" (the one that hold the repo clone)
listed as module (see known issue JBIDE-13862). But for projects created via Application
wizard, which have the magic project listed as module, the whole deployments page is
frozen.
I did a quick thread dump inspection but could not depict any suspicious thread:
http://fpaste.org/56871/47676913/
This looks rather like an UI issue, maybe some control overlay that's stealing mouse
clicks or something. In a quick review of the code I could not see anything suspicious.
Needs further investigation.
I dont see right now whats causing this. Any ideas, Rob?
was (Author: adietish):
i merged this locally and this works fine for adapters that I create via Server
adapter wizard. Those dont have the "magic project" (the one that hold the repo
clone) listed as module (see known issue JBIDE-13862). But for projects created via
Application wizard, which have the magic project listed as module, the whole deployments
page is frozen. I dont see right now whats causing this. Any ideas, Rob?
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
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