[TRINIDAD-1077] jdev plugin library configuration

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.2.6-plugins
• Component/s: Plugins
• Environment: both windows and linux
• Assignee: Unassigned
• Reporter: Nararasimhaiah Sreehari
• Created: 14/May/08 22:56
• Updated: 14/May/08 22:59

Description

When the project path and the library path are absolute paths are not the same but have a common folder name in the path, the libarary definition constructs incorrectly.
eg:
project path d:\work\nsreehar\myapp\....
and path to library is
c:\documents and settings\nsreehar\.m2\repository\org\.....

Since the project is on d drive, the full path should be picked up. Instead, the plugin interprets this as having a single common path folder.
The problem exists in both windows as well as linux.

The problem appears to go away when the following patch

1665c1674
< if (sourcePaths[i].equals(targetPaths[i]))

—
> if (sourcePaths[i].equals(targetPaths[i]))

1666a1676,1677
> else
> break;

Please note that the fix described in TRINIDAD-331 has already been applied.