v2.2.16

Release aligned with Eclipse 2021-03 simultaneous release.

Last release with support for JavaSE-1.8, next releases will use JavaSE-11.

v2.2.15

This release is aligned with Eclipse 2020-06 simultaneous release.
Java 1.8 or better required.

Integrated submitted patch for #7

Resource leakage patch #6 breaks the on-the-fly downstream processing of the input XML stream. ''This patch for #7 forces to finish the parse before exiting the (loading) function, but loses the on the-fly-ness from the parser.''

Integrated submitted patch for #6

This release integrates submitted patch to fix resource leakage issue #6. It is distributed according to the versioning of published Update Sites, thus fixes #5.

Support of long in markings and inscriptions

This release brings a _backwards incompatible change_ to the API, but has not been properly tagged. It is more than a simple compatible bug fix, as version 2.2.10 would have suggested.

_It should have become 3.0.0_ instead to warn you about the incompatible change. Since it has already been propagated to Maven Central, you should either stick to 2.2.9, or migrate to 2.2.10 with the knowledge of the incompatible change, explained hereafter.

The standard sets no upper bound limit on the value space of integers to set markings and inscriptions in the nets. The corresponding XML type represents the mathematical concept of non-negative integers or positive integers. Therefore, their value space is the infinite set, i.e. {0, 1, 2, ...} for non-negative integers, or {1, 2, 3, ...} for positive integers. The implementation should then use at least the type "long" for their representation.