Community
Participate
Working Groups
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).
Charles - come by, and we can discuss this defect
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.
Re-assigning owner for now....
We do not have a need for this (implemented a work-around in our logic) so lowering priority.