[
https://issues.jboss.org/browse/JBIDE-14791?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-14791:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure you have an as7 server adapter
# ASSERT: make sure you have a WTP project in your workspace that you can deplyo to as7
# EXEC: drag and drop the project to your server adapter
# EXEC: double click as7 server adapter, in the upcoming server editor choose
"deployments" tab
Result:
The deployments table is disabled
!deployments-greyed-out.png!
Expected result:
The deployments table is enabled, I should be able to edit the deployments
was:
# ASSERT: make sure you have an as7 server adapter
# ASSERT: make sure you have a WTP project in your workspace that you can deplyo to as7
# EXEC: drag and drop the project to your server adapter
# EXEC: double click as7 server adapter, in the upcoming server editor choose
"deployments" tab
Result:
The deployments table is disabled
Expected result:
The deployments table is enabled, I should be able to edit the deployments
cannot rename deployed modules in AS7 server adapter
----------------------------------------------------
Key: JBIDE-14791
URL:
https://issues.jboss.org/browse/JBIDE-14791
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift, server
Affects Versions: 4.1.0.Beta2
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.1.0.Beta2
Attachments: deployments-greyed-out.png
openshift nor as7 seem to anymore be able to rename their deployed modules.
i.e. to be able to deploy testapp.war as ROOT.war for having it deployed in /
--
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