Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 365529

Summary:	Changing the Deploy Path in the Deployment Assembly can lead to unexpected results
Product:	[WebTools] WTP Java EE Tools	Reporter:	Mauro Molinari <mauromol>
Component:	wst.web	Assignee:	jst.j2ee <jst.j2ee-inbox>
Status:	NEW ---	QA Contact:	Chuck Bridgham <cbridgha>
Severity:	normal
Priority:	P3
Version:	3.3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Mauro Molinari

2011-12-04 14:30:32 EST

Build Identifier: 20110916-0149

When you change the deploy path of a project in the deployment assembly, you may get unexpected results if you remove the archive file name.

Reproducible: Always

Steps to Reproduce:
1. create a Dynamic Web Project "TestDWP"
2. create a Utility Project "TestUtility"
3. go to the Deployment Assembly of "TestDWP", Add... | Project | Next > | select TestUtility | Finish
4. the default Deploy Path for the added project is WEB-INF/lib/TestUtility.jar (by the way: why WTP 3.3 is now setting the archive name by default? In older versions of WTP the default deploy path would have been just WEB-INF/lib and I personally preferred the old behaviour, which did not create a dependency to the utility project name...)
5. change the Deploy Path to WEB-INF/lib and press OK
6. type Ctrl+Shift+R and open the file .settings/org.eclipse.wst.common.component for TestDWP project
7. look at the <dependent-module> element for the TestUtility project

EXPECTED RESULT
<dependent-module deploy-path="/WEB-INF/lib" handle="module:/resource/TestUtility/TestUtility">

ACTUAL RESULT
<dependent-module archiveName="lib" deploy-path="/WEB-INF" handle="module:/resource/TestUtility/TestUtility">