[Bug 2766] - own manifest- file is ignored even it is declated in jar task

[bu...@apache.org]

PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2766

*** shadow/2766	Tue Jul 24 07:41:45 2001
--- shadow/2766.tmp.18713	Sat Jul 28 07:21:50 2001
***************
*** 25,28 ****
  But ant still is taking a blank manifest file instead of my manifest file. How 
  can I get this solved?
  Thanks a lot
! Georg
--- 25,39 ----
  But ant still is taking a blank manifest file instead of my manifest file. How 
  can I get this solved?
  Thanks a lot
! Georg
! 
! ------- Additional Comments From conor@cortexebusiness.com.au  2001-07-28 07:21 -------
! What you have given should work if ${mmanifest} is a valid property. Is the 
! spelling there correct? I would expect an exception, though, if the property 
! was not valid. When you say you get a blank manifest file, what exactly do you 
! mean by blank. Does it not have Created-By: Ant 1.3 and the Manifest-Version 
! header. If it doesn't have these then perhaps ${mmanifest} is pointing to a 
! blank file.
! 
! Finally, I have just committed new Manifest handling code. Could you try a 
! nightly build in the next few days and see what results that gives.