ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 48152] Task ManifestClassPath fail to find suitable relative path
Date Thu, 07 Jan 2010 12:27:05 GMT changed:

           What    |Removed                     |Added
             Status|NEEDINFO                    |NEW

--- Comment #3 from 2010-01-07 04:27:03 UTC ---
Sorry, for the late reply. It took me some time to figure out whether setting
maxParentLevels to a higher value solves the problem. 
The result is: It does not. More precisely it does fix the problem on Windows
machines, but not on Unix machines (where we initially discovered the bug, but
were not aware of the fact the the bug is OS-specific). 
I'll attach a second version of the test case that shows the problem. It needs
to run on a Unix (or Mac).

Test case A shows that setting maxParentLevels to value that is too low,
results in the "Can't find suitable relative path" exception. I do not
understand why setting maxParentLevels is needed and why the default value is 2
instead of Integer.MAX_VALUE, but thats a different issues. Can you explain

Test case B shows that setting maxParentLevels to the number of segments in the
path that is used as starting location results in an

Test case C shows that setting maxParentLevels to a number greater than the
number of segments result in a NullPointerException.

Please let me know if further information is required.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

View raw message