1.3.1

• Fixed implementation of PosixFileAttributes.permissions() to return a modifiable set as specified in the Javadoc for that method. (7c6a430)
• Increase precision of SystemFileTimeSource. (bdcd240)

1.3.0

Maven dependency:

<dependency>
  <groupId>com.google.jimfs</groupId>
  <artifactId>jimfs</artifactId>
  <version>1.3.0</version>
</dependency>

What's new in 1.3.0

• Officially dropped support for Java 7, and restored accidentally dropped support for Java 8. (5b60a42)
• Added an Automatic-Module-Name to the jar for modules support. (6a057ff)
• Fixed several bugs with the behavior of FileChannel.transferFrom. (ee785ea)
• Added FileTimeSource and made it possible to set a FileTimeSource in the Configuration of a file system. (139c10e)

1.2

Maven dependency:

<dependency>
  <groupId>com.google.jimfs</groupId>
  <artifactId>jimfs</artifactId>
  <version>1.2</version>
</dependency>

Javadoc for the release can be viewed at: http://google.github.io/jimfs/releases/1.2/api/docs/
API diffs between Jimfs 1.1 and this release can be viewed at: http://google.github.io/jimfs/releases/1.2/api/diffs/

What's new in 1.2

• Various bug fixes.

1.1

Jimfs 1.1 final release.

Maven dependency:

<dependency>
  <groupId>com.google.jimfs</groupId>
  <artifactId>jimfs</artifactId>
  <version>1.1</version>
</dependency>

Javadoc for the release can be viewed at: http://google.github.io/jimfs/releases/1.1/api/docs/
API diffs between Jimfs 1.0 and this release can be viewed at: http://google.github.io/jimfs/releases/1.1/api/diffs/

This release contains no changes from 1.1-rc1.

What's new in 1.1

• Now possible to configure the rate at which a WatchService polls by calling setWatchServiceConfiguration(WatchServiceConfiguration.polling(interval, timeUnit)) when building a Configuration. (#14)
• Now possible to get the default Configuration (based on the current operating system) that is used when calling the Jimfs factory methods that do not take a Configuration parameter, via Configuration.forCurrentPlatform(). Mainly useful if you want to create a slightly modified (e.g. with a different WatchService polling rate) version of that Configuration.
• URL objects can now be created from Jimfs Paths (using path.toUri().toURL()). Such URLs support reading the contents of the file through an InputStream, with behavior similar to that of a normal file: URL object. (#13)
• URIs for directories now end in a trailing /. (#16)
• Fixed an issue with environments where Java SDK code (such as the FileSystems class and by extension the FileSystemProvider implementations it loads as services) and user code (including the Jimfs entry point class) are loaded by different classloaders. (#18)

1.1-rc1

First release candidate for Jimfs 1.1.

Maven dependency:

<dependency>
  <groupId>com.google.jimfs</groupId>
  <artifactId>jimfs</artifactId>
  <version>1.1-rc1</version>
</dependency>

Javadoc for the release can be viewed at: http://google.github.io/jimfs/releases/1.1-rc1/api/docs/
API diffs between Jimfs 1.0 and this release can be viewed at: http://google.github.io/jimfs/releases/1.1-rc1/api/diffs/

What's new in 1.1

• Now possible to configure the rate at which a WatchService polls by calling setWatchServiceConfiguration(WatchServiceConfiguration.polling(interval, timeUnit)) when building a Configuration. (#14)
• Now possible to get the default Configuration (based on the current operating system) that is used when calling the Jimfs factory methods that do not take a Configuration parameter, via Configuration.forCurrentPlatform(). Mainly useful if you want to create a slightly modified (e.g. with a different WatchService polling rate) version of that Configuration.
• URL objects can now be created from Jimfs Paths (using path.toUri().toURL()). Such URLs support reading the contents of the file through an InputStream, with behavior similar to that of a normal file: URL object. (#13)
• URIs for directories now end in a trailing /. (#16)
• Fixed an issue with environments where Java SDK code (such as the FileSystems class and by extension the FileSystemProvider implementations it loads as services) and user code (including the Jimfs entry point class) are loaded by different classloaders. (#18)

1.0

Final 1.0 release. This release contains no changes from 1.0-rc3.

This release can be used with Maven as:

<dependency>
  <groupId>com.google.jimfs</groupId>
  <artifactId>jimfs</artifactId>
  <version>1.0</version>
</dependency>

Javadoc for the release can be viewed at: http://google.github.io/jimfs/releases/1.0/api/docs/

1.0-rc3

Third release candidate. This release changes the package for all classes from com.google.jimfs to com.google.common.jimfs.

This release can be used with Maven as:

<dependency>
  <groupId>com.google.jimfs</groupId>
  <artifactId>jimfs</artifactId>
  <version>1.0-rc3</version>
</dependency>

1.0-rc2

Second release candidate, containing a number of fixes and usability improvements.

This release can be used with Maven as:

<dependency>
  <groupId>com.google.jimfs</groupId>
  <artifactId>jimfs</artifactId>
  <version>1.0-rc2</version>
</dependency>

Notable changes:

• FileSystem instances are now cached statically, so even if multiple instances of JimfsFileSystemProvider are created, they'll share the same cache of file systems. This is meant to ensure that what ClassLoader happens to load JimfsFileSystemProvider has no effect on behavior (the provider instance itself is only cached if it can be loaded by the system ClassLoader).
• FileSystem instances are now cached with weak references, allowing them to be garbage collected when no references remain even if close() has not been called. This is preferable in most cases. The only negative impact is that if you wish to hold on to a URI (either for a FileSystem or a Path in that file system) and later use it to retrieve that FileSystem/Path, it may not work unless you ensure that a strong reference to the FileSystem is held somewhere.
• Closing a FileSystem now closes all open streams, channels, etc. for that file system and causes most Files methods to throw ClosedFileSystemException.
• The jar now has OSGi metadata.

1.0-rc1

Initial release candidate, mainly so there's an artifact available in Maven Central that people can use.

This release can be used with Maven as:

<dependency>
  <groupId>com.google.jimfs</groupId>
  <artifactId>jimfs</artifactId>
  <version>1.0-rc1</version>
</dependency>