Bump openpojo from 0.8.1 to 0.8.13

[dependabot]

Bumps openpojo from 0.8.1 to 0.8.13.

Release notes

Sourced from openpojo's releases.

OpenPojo 0.8.13

Fixed

1. Issue #130, OpenPojo should now be able to be loaded and run in jdk > 1.8.
2. Issue #132, Testing Serializable now supports strict as well as non-strict serialization validation.
   • If you set Strict to true, and have an interface in your pojo, that interface must also extend serializable.
   • Default serialization is not strict (useStrictValidation = false).

OpenPojo 0.8.12

Added

1. PojoClass now supports getEnclosingClass if for nested classes, will return null if class isn't nested.

Fixed

1. Issue #119, OpenPojo was failing to construct non static nested class when class had declared constructor with non-generic parameters. (Thank to myron0815)

OpenPojo 0.8.11

Added

1. Issue #127 Support for JUnit 5 @Test annotation (Thanks to @icenfrosty)
2. Issue #125 Support for ASM 7.0 (Thanks to @the4dk).

Fixed

1. Issue #123 Some classes retrieve their source Jar file as file:/path instead of file:///path (Thanks to @max-norris & @myron0815).

OpenPojo 0.8.10

Added

1. Issue #113 Support for randomly generating BufferedImage. (Thanks to panosgit)

Fixed

1. Issue #95 AttributeHelper was stripping out the prefixes from fields regardless of registration scope (causing exceptions). Will now allow you to use the AttributeHelper registering Prefix as guidance not given, enabling you to migrate out of your prefix architecture if needed. (Thanks to Yky)
2. Better version detection for ASM versions, there was a corner case when ASM pre-5.0 was loaded causing unexpected failure due to changes in ASM pre-5. OpenPojo will now throw appropriate exception if ASM pre-5.0 is detected or 6.0 or higher.

OpenPojo 0.8.9

Fixed

1. Removed an accidental include of Log4J logger in SerializableTester, now its logging appropriately to OpenPojo's logging framework.
2. Fixed an issue when abstract classes were failing generation for testing.
3. Minor fixes to PrincipleName random generation to make it more robust on JDK 1.5.

OpenPojo 0.8.8

Added

1. Serializable tester, now you can test all your serializables by adding "SerializableTester" to the validator, did you know you can also enumerate all serializables in your code with this one call:

      PojoClassFactory.enumerateClassesByExtendingType("your.top.level.package", Serializable.class, null);

2. OpenPojo will now generate stub methods for all abstract methods in an abstract class being tested. Those methods will return random values based on the return type.

Changed

1. Issue #102 Now you can pull the PojoClass if you have the PojoField.

Fixed

1. Issue #89 If an abstract class was being tested and during one of the methods being tested a call toString() was made and toString() was declared abstract, an error used to be thrown, now OpenPojo will dispatch the toString() to BusinessIdentity.toString() to print the class name and memory address per standard. While trouble shooting this issue also fixed an issue when an abstract class under testing had constructor(s) defined that had parameters in them was throwing errors. (Thanks to Michel W.)
2. Issue #107 When a erroneously detecting serialVersionUID was a shadowed field. (Thanks to Henrik V.)
3. Issue #112 Failure for OpenPojo to randomly generate appropriate XMLGregorianCalendar object.

... (truncated)

Commits

• 3b8f736 [maven-release-plugin] prepare release openpojo-0.8.13
• cba7a17 Cleaning up pom.xml
• 3c8738f cleaning up JavaDoc
• b5e2375 Minor cleanup.
• 30aa574 Fixing JaCoCo instrumentation.
• c7db7a5 Upgrading versions to latest libraries.
• e860a98 Upgrading versions to latest libraries.
• 823d42b Fixing formatting
• fc4fd77 Fixed issue #130
• 3cf2b06 Minor cleanup
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)