Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348961 - Deployment Assembly page changes too many files
Summary: Deployment Assembly page changes too many files
Status: CLOSED DUPLICATE of bug 197221
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.2.3   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: jst.j2ee CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-09 16:38 EDT by Gary Karasiuk CLA
Modified: 2011-06-10 10:17 EDT (History)
0 users

See Also:

Attachments
Changed files (20.85 KB, image/gif)
2011-06-09 16:38 EDT, Gary Karasiuk CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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 ***