[
https://issues.jboss.org/browse/JBIDE-20711?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-20711:
-------------------------------------
Whether hand-edited or changed via API, the fact is the property int he IModule is static
and prone to get out of date. Also, there will be users that DO hand-edit that field (i
do, all the time) and their tools shouldn't simply break on them when they do this.
Changing deploy-name in component xml file will not take effect
---------------------------------------------------------------
Key: JBIDE-20711
URL:
https://issues.jboss.org/browse/JBIDE-20711
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server, upstream
Affects Versions: 4.3.0.CR1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.3.1.Final, 4.4.x
Steps to replicate:
1) Create a dynamic web project TestProject
2) Create a server
3) Add/Remove action in servers view. You will see the module name is TestProject
4) Open the component.xml file in .settings folder and change deploy-name to some new
value (RobsTest)
5) Add/Remove, note module name didn't change
6) Publish deployment, note its still deploying as TestProject
7) Close project, then re-open it
8) Add/Remove action, note the module now reads TestProject (RobsTest) (or similar)
9) Publish, note module is deployed as RobsTest.war
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)