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

Bug 348961

Summary: Deployment Assembly page changes too many files
Product: [WebTools] WTP Java EE Tools Reporter: Gary Karasiuk <karasiuk>
Component: jst.j2eeAssignee: jst.j2ee <jst.j2ee-inbox>
Status: CLOSED DUPLICATE QA Contact: Chuck Bridgham <cbridgha>
Severity: normal    
Priority: P3    
Version: 3.2.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Changed files none

Description Gary Karasiuk CLA 2011-06-09 16:38:15 EDT 
I am running Helios JEE SR2 with a Tomcat server.

I added some projects to my Dynamic Web Project through the Deployment Assembly
properties page.

This is a follow on to Bugzilla 348957.

When I look at the files that this action changed, I feel that it has changed too many of my files. It should not change my .classpath files and it should not add  "empty" MANIFEST.MF files.
Comment 1 Gary Karasiuk CLA 2011-06-09 16:38:54 EDT 
Created attachment 197737 [details]
Changed files
Comment 2 Gary Karasiuk CLA 2011-06-09 16:44:05 EDT 
I have attached a screenshot that shows the files that were changed as a result of adding projects via the Deployment Assembly page.

The code in these "utility" projects, is for the most part POJOs. I want to be able to reuse this code in OSGi applications, simple Java applications, and as utility code to my web projects. I don't want my classpath changed (for no good reason) as that will break my code in it's other uses.

I undid the classpath and MANIFEST.MF changes, and as near as I can tell, everything works correctly.
Comment 3 Chuck Bridgham CLA 2011-06-10 10:17:53 EDT 

*** This bug has been marked as a duplicate of bug 197221 ***