Use fully qualified path for legacy name field option

Merged #40. This reverts to the pre-v2 behavior of requiring a fully-qualified name match for the legacy name field option. This is a breaking change if you use the legacy name feature. Otherwise this is a no-op. The README has been updated so the example uses a fully-qualified name.

Add uint64 support and propagate null timestamps and dates

Merged #29 and #34.

Add Schema Name and fix with Bytes issue

Merged #15, #20, and #21

Fix for oneOf default handling

Merge pull request #12 from blueapron/jitpack-publish-to-maven

Use Jitpack to publish to Maven

Kafka Connect 3.2.x Stable Release with Jitpack

Publish to the Jitpack repository

v2.0.0: Merge pull request #8 from blueapron/add-maven-packaging-component

Add the Maven packaging component

Kafka Connect 3.2.x Stable Release

Uses Confluent Platform 3.2.x