https://issues.apache.org/bugzilla/show_bug.cgi?id=52227
Bug #: 52227
Summary: manifestclasspath makes paths relative to build dir
and not jarfile
Product: Ant
Version: 1.8.2
Platform: PC
Status: NEW
Severity: normal
Priority: P2
Component: Core tasks
AssignedTo: [email protected]
ReportedBy: [email protected]
Classification: Unclassified
Created attachment 27974
--> https://issues.apache.org/bugzilla/attachment.cgi?id=27974
test build file, sample jar and class
not sure if this is a windows issue.
if my build folder is d:/prog/j/anttestManifestClasspath
but the final run folder is d:/run/anttestManifestClasspath
i run ant from the build folder with a manifestclasspath task and jar task with
manifest that uses the classpath created here, the relative folders are not to
final jar file in d:/run/anttest but to my build folder.
I think its a bug as the full path to the final jar is given to
manifestclasspath task so the paths should be relative to that.
Would suggest the documentation reflect this if its as expected.
Workaround exists - call another build file from the main file and keep that
build file's base dir as the run folder
Important when the build file is old and has relative paths to it so we cant
change from where the build is started nor can we change the base dir
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
