Bug 164829 - 1.0.x J2EE module dependencies cannot be completely removed in 1.5
Summary: 1.0.x J2EE module dependencies cannot be completely removed in 1.5
Status: NEW
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Carl Anderson CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-16 11:36 EST by Rob Frost CLA
Modified: 2007-08-24 16:41 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rob Frost CLA 2006-11-16 11:36:58 EST
In 1.0.X, J2EE module dependencies were represented using entries in the following files:

.project
.classpath
.component
MANIFEST.MF

(WEB-INF/lib dependencies where represented by .classpath and .component)

In 1.5, only a MANIFEST.MF reference is used for module dependencies and only a component file reference is used for WEB-INF/lib dependencies.

This means that when a user attempts to remove a 1.0.X dependency in a 1.5 workspace, stale references will be left (i.e. an explicit .classpath ref, etc.) 

The module migrator logic will need to be enhanced to cover this use case (i.e. add the appropriate marker and, when executed, remove the now unused references).
Comment 1 Chuck Bridgham CLA 2006-11-28 11:45:18 EST
Charles - come by, and we can discuss this defect
Comment 2 Chuck Bridgham CLA 2007-01-29 11:25:43 EST
Hi Rob,

While I agree these redunant entries should be detected and cleaned up, I'm not so sure of the severity at this point, and perhaps should be looked at for 2.0.

I'm untargetting - please add your suggestions.
Comment 3 Chuck Bridgham CLA 2007-02-19 10:25:07 EST
Re-assigning owner for now....
Comment 4 Rob Frost CLA 2007-08-24 16:41:44 EDT
We do not have a need for this (implemented a work-around in our logic) so lowering priority.