Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: 8
Affects Version/s: 6u24
Component/s: tools
Labels:
- bugdb_13728559

Subcomponent:
jar
Resolved In Build:
b32
CPU:

generic
OS:

generic
Verification:
Verified

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-2222025	7u6	Sean Coffey	P3	Closed	Fixed	b03
JDK-2223416	6u34	Sean Coffey	P3	Resolved	Fixed	b01
JDK-2223415	6u33	Sean Coffey	P3	Resolved	Fixed	b31
JDK-2223414	6u32	Sean Coffey	P3	Resolved	Fixed	b31
JDK-2222026	6u31-rev	Sean Coffey	P3	Resolved	Fixed	b25

SHORT SUMMARY:Jar tools fails to generate manifest file correctly when
boundary condition hit in Manifest.FastInputStream class
INDICATORS: jar tool fails to add attributes to Manifest file
COUNTER INDICATORS:
TRIGGERS: A manifest file is supplied of unique size so that a
Manifest.FastInputStream.fill() call is made just before EOF of Manifest file
is reached.
KNOWN WORKAROUND: Add an extra empty line to Manifest file supplied to jar
command
PRESENT SINCE: FCS
HOW TO VERIFY: See bug DB descrition
NOTES FOR SE:
REGRESSION: No.

backported by

JDK-2222026 Jar tools fails to generate manifest correctly when boundary condition hit

Resolved

JDK-2223414 Jar tools fails to generate manifest correctly when boundary condition hit

Resolved

JDK-2223415 Jar tools fails to generate manifest correctly when boundary condition hit

Resolved

JDK-2223416 Jar tools fails to generate manifest correctly when boundary condition hit

Resolved

JDK-2222025 Jar tools fails to generate manifest correctly when boundary condition hit

Closed

Assignee:: Sean Coffey

Reporter:: Shadow Bug

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Created:: 2012-02-24 09:00

Updated:: 2014-11-19 11:08

Resolved:: 2012-04-20 15:54

Imported:: 16/Sep/12 3:46 PM

Indexed:: 18/Jul/12 10:22 AM

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates