[
https://issues.jboss.org/browse/JBIDE-20711?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-20711:
-------------------------------------
Then I changed the deploy-name in
TestProject/.settings/org.eclipse.wst.common.component (in vi in terminal),
This usecase is never expected to work without a refresh. If you change the file outside
of the workspace, we cannot expect eclipse to notice that.
My point was if you change the contents **inside** eclipse, it works without a refresh.
With this in mind, I still suggest this is working exactly as expected.
[~mmalina] Please close the issue if you can verify that modifying the xml file inside
eclipse is sufficient without a refresh. We cannot handle the situation of users editing
files outside eclipse.
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.4.3.AM2
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
(v7.2.3#72005)