http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1453
*** shadow/1453 Mon Apr 23 23:25:53 2001 --- shadow/1453.tmp.23452 Tue Apr 24 17:29:23 2001 *************** *** 5,11 **** | Status: NEW Version: 1.3 | | Resolution: Platform: PC | | Severity: Normal OS/Version: Windows NT/2K | ! | Priority: High Component: Core tasks | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | --- 5,11 ---- | Status: NEW Version: 1.3 | | Resolution: Platform: PC | | Severity: Normal OS/Version: Windows NT/2K | ! | Priority: Medium Component: Core tasks | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | *************** *** 37,40 **** a) a small test case b) the resulting jar file that does not work for you ! as this works perfectly well for me (using W2K/SP1 and java version "1.3.0". --- 37,46 ---- a) a small test case b) the resulting jar file that does not work for you ! as this works perfectly well for me (using W2K/SP1 and java version "1.3.0". ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-04-24 17:29 ------- ! One more note - As I was creating the attached test case, I discovered that ! this only occurs when I perform the build on a drive mapped to a network ! share. Files build with the Java2 SDK "jar" command on the network drive are ! still readable.
