https://issues.apache.org/bugzilla/show_bug.cgi?id=44915
Summary: manifestclasspath interferes with other build targets
when the classpath directory does not exist
Product: Ant
Version: 1.7.0
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: Build Process
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
I have a 'clean' target which deletes my build/lib and dist directories.
I encountered a build error after build/lib was created and when I re-ran ant I
get a error "48: Jar's directory not found". Line 48 is the manifestclasspath
piece.
Re-running with 'ant clean' gets same error, even though 'clean' never attempts
to create the jar and hence should never need to look to the manifestclasspath.
Removing manifestclasspath, rebuilding, adding manifestclasspath and rebuilding
is the workaround I am using.
Incidentally if you put a full dependency (e.g. ant 'all') for
clean,copystatic,compile,jar,install there is NO error encountered so full
successful builds aren't affected by this issue.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
