Releases: 3breadt/dd-plist
Releases · 3breadt/dd-plist
Release 1.28
Added
NSObjects.getLocationInformation()
provides information about an object's location within the parsed property list file (e.g. line number)PropertyListFormatException.getLocationInformation()
provides information about where the parsing error occurred- Added
module-info
to improve usability of this library for Java 9 and later
Improved
PropertyListFormatException
's messages now include more detailed information about where the parsing error occurred
Release 1.27
This release contains several important bugfixes related to malformed property lists that could cause endless loops and undocumented exceptions.
Features
- Added support for storing null objects in
NSSet
- All NSObjects now implement
Comparable<NSObject>
- Improved parsing of binary property lists containing multiple references to the same object instance
- Added support for Base64 NSData representation in GNUstep ASCII property lists (Issue #57)
- Added support for creating
UID
instances fromBigInteger
instances (Issue #38)
Bugfixes
Release 1.26
Bug Fixes / Improvements
- Reduced unnecessary memory allocation when parsing binary property lists, which could cause OutOfMemoryErrors when handling corrupted files (Issue #72)
Release 1.25
What's Changed
- XML and ASCII parser improvements for reading data from String/Reader by @jpstotz in #71
- Moved methods related to writing and converting property lists into separate classes:
ASCIIPropertyListWriter
,BinaryPropertyListWriter
,XMLPropertyListWriter
andPropertyListConverter
. The old methods for saving and converting inPropertyListParser
have been marked as deprecated. - Added method overloads for reading/writing property lists using
java.nio.file.Path
instances
New Contributors
Full Changelog: v1.24.0...v1.25.0
Release 1.24
What's Changed
- Updated to Java 8
- Parsing XML property lists from InputStreams no longer closes the InputStream (Issue #55)
- Fixed invalid XML property lists being created when NSString instances contained characters that are illegal in an XML document
- Fixed
toJavaObject()
not working for NSData (Issue #59) - Fixed ArrayIndexOutOfBoundsException when parsing certain ASCII property lists (Issue #67)
- Fixed parsing of ASCII and XML property lists that are encoded in UTF-16 or UTF-32
Full Changelog: dd-plist-1.23...v1.24.0
Release 1.23
Changes since version 1.22:
- Added support for parsing and encoding NSNumbers with the value NaN (Issue #54)
Release 1.22
Changes since version 1.21:
- Fixed converting NSNumber instances created from integers to float or double (Issue #49)
Release 1.21
Changes since version 1.20:
- All
NSObject
instances are now cloneable. CallingNSObject.clone()
will return a deep copy of the object. - Binary Property Lists
- Fixed
OutOfMemoryError
when parsing binary property list files with an invalid object table (#42). - Improved exceptions that are thrown in case of a corrupted or invalid object table
- Fixed
- ASCII Property Lists
- The text encoding that is used when parsing a property list can now be configured (#48, #47)
- UTF-16 and UTF-32 encoded property lists with BOM are now automatically detected
- Escaped single quotes are now properly unescaped (#45)
- Improved exceptions that are thrown when encountering an invalid escape sequence
Release 1.20
Release 1.19
Changes from 1.18 to 1.19:
- Disable automatic unpacking of NSData content that begins with a GZIP header when parsing XML property lists. This fixes exceptions if the data is not actually GZIP compressed. See issue #31.