Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 330286 - Deployment Assembly not using simplest default runtime path for classpath dependencies
Summary: Deployment Assembly not using simplest default runtime path for classpath dep...
Status: RESOLVED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2.3   Edit
Assignee: Jason Peterson CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-15 15:30 EST by Jason Peterson CLA
Modified: 2010-11-17 09:50 EST (History)
3 users (show)

See Also:
cbridgha: review+

Attachments
patch (3.77 KB, patch)
2010-11-15 15:30 EST, Jason Peterson CLA 		no flags Details | Diff
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 Jason Peterson CLA 2010-11-15 15:30:46 EST 
Created attachment 183161 [details]
patch

When calculating the default runtime path for a classpath dependency mapped to an EE 5/6 EAR the simplest path is not being returned.  For example if I have a utility project mapped to /foo/bar and foo is the EAR's library directory the default runtime path returned would be "../../../foo".  The first "../" is specifying that it maps to the EAR.  The next two are because it is always moving up to the EAR's root directory and then appending the library directory.  It should have just moved up one directory right to the EAR's library directory.
The simplest and best returned path would have been "../../".
Comment 1 Jason Sholl CLA 2010-11-16 09:18:53 EST 
Code checked into 32M and HEAD for WTP 3.2.3 and 3.3
Comment 2 Chuck Bridgham CLA 2010-11-17 09:50:20 EST 
approved