Releases: OCFL/ocfl-java
v2.2.1
v2.2.0
v2.1.0
Note that this version contains breaking changes that affect how the repository is configured when using S3 storage. You now must configure an async client and a transfer manager. See the usage guide for more details. These changes should result significant performance improvements when writing to S3 storage.
Fixed
ObjectVersionId.equals()
no longer throws an error for HEAD versions: #110- Deleting an object in S3 that contains more than 1,000 files now works.
- Writing to files with identical content and writing the first file a second time to the same version no longer causes
the staged file to be erroneously deleted.
Changed
- Breaking: A
S3AsyncClient
S3 client now must be used with ocfl-java-aws, and the sync version is no longer supported. - Breaking: A
S3TransferManager
must now be set when using S3 storage. - ocfl-java-aws now uses the S3 Transfer Manager
to upload files to S3. See the usage guide for more details. - ocfl-java-aws now concurrently uploads files when writing an object to S3. This should improve object write performance.
- The
OcflObjectUpdater
was updated to be thread safe, enabling concurrently writing files to it. This may speed up
writing a large number of files to an object. See the usage guide for
more details.
v2.0.1
v2.0.0
The primary change here is the move from edu.wisc.library.ocfl
to io.ocfl
. If you were using the previous version, you will need to change the artifact group name and update all of the package names in your source. Only the package names changed. There were no additional breaking changes.
Fixed
- Delete old revision markers after creating a new mutable HEAD revision: #91
- Use an AtomicBoolean to track if the repository has been closed: #87
Changed
- Renamed the package root from
edu.wisc.ocfl
toio.ocfl
- Prefer
Files.find()
toFiles.walk()
: #92
v1.5.0
This release adds support for OCFL spec version 1.1. By default, all newly create repositories will now be OCFL 1.1 repositories. Existing repositories will not be upgraded automatically. See Upgrading OCFL Repositories in the readme for details on how to upgrade existing repositories and objects.
There are no functional differences between 1.0 and 1.1. The 1.1 release mostly clarifies some of the 1.0 language so that it is more explicit.