Loading... (original) (raw)

Log inSkip to main contentSkip to sidebar

Java Bug System

Uploaded image for project: 'JDK'

  1. JDK
  2. JDK-8034773

(zipfs) newOutputstream uses CREATE_NEW when no options specified

Log In

[Resolved](# "Resolved
A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.")

Export

XMLWordPrintable

Issue Fix Version Assignee Priority Status Resolution Resolved In Build
JDK-8084288 emb-9 Xueming Shen P3 Resolved Fixed team
JDK-8237462 openjdk8u252 Xueming Shen P3 Resolved Fixed b01

As noted here:
http://mail.openjdk.java.net/pipermail/nio-dev/2014-February/002524.html

If newOutputStream is called without any options then it uses CREATE_NEW rather than CREATE + TRUNCATING_EXISTING.

backported by

Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8084288 (zipfs) newOutputstream uses CREATE_NEW when no options specified

Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8237462 (zipfs) newOutputstream uses CREATE_NEW when no options specified

Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8233103 (zipfs) newOutputstream uses CREATE_NEW when no options specified

relates to

Bug - A problem which impairs or prevents the functions of the product. JDK-8233015 (zipfs) Files.newOutputStream on a ZipFileSystem path leads to java.nio.file.FileAlreadyExistsException

Assignee:

sherman Xueming Shen

Reporter:

alanb Alan Bateman

Votes:

0 Vote for this issue

Watchers:

4 Start watching this issue

Created:

2014-02-12 04:12

Updated:

2020-01-16 23:41

Resolved:

2015-05-27 12:30