How do I verify a
This is a minor feature enhancement for Versioneer.
1: Additional exceptions have been added
2: Code coverage is now at 100% of classes and methods, and 95.2% of lines
3: JaCoCo integration has been removed
4: Fixed @since and @version tags in FourPartVersion
This is a minor (yet backward-incompatible) update to Versioneer.
The major points for concern are:
1: GenericVersion has been replaced with FourPartVersion
2: Version.toGenericVersion() has been replaced with Version.toFourPartVersion()
3: VersionType.RC has been replaced with VersionType.RELEASE_CANDIDATE. The postfix, however, is still "-RC"
Removed some unneeded constructors from Version
Removed an unneeded constructor from InvalidVersionType
Integrated testing with the JaCoCo code analysis tool
Removed most @version and @since tags in tests. Lost track of what actually started where, so it was easier to just remove them.
Other minor documentation changes
Properly implemented tiered constructors in Version sub-classes
Added some annotations that may be used
Added the following annotations:
This is the second feature update for Modger. It is not backwards-compatible with 184.108.40.206 in most cases, and simply requires a renaming of all "AbstractVersion" references to "Version"
Renamed AbstractVersion to Version
Load Versions dynamically from a String
Some URL fixes in the POM file
Changed the Maven group ID
Multiple Maven fixes
Some more constructors in AbstractVersion
Fixed output of code names with toString
This release introduces the following features:
Version code names
Removal of equals(Object) from Version classes - All handled by AbstractVersion
The following bug is fixed:
https://bugs.launchpad.net/versioneer/+bug/928470 - Numeric parts of Version classes can be negative
The first feature upgrade for Versioneer, mainly making Versioneer easier to use
Version class cloning
More details in the POM file
Implemented hashCode() in Version