Minor clean up

[PiggyPiglet]

• Implements jetbrains annotations instead of manual null checks. These will throw errors if a null value is provided, while being a far cleaner approach to the issue.
• Cleaned up badly formatted javadocs.
• Removed redundant method modifiers (final methods in a final class)
• Applied the final keyword where appropraite
• Removed redundant constructor

Keep in mind, with the annotations dependency, due to limitations of maven, the scope must be set to compile for the tests to pass. When shipping the library however, the annotations dependency should have the provided scope. I'd recommend switching to gradle to circumvent this issue.

[lewysDavies]

Awesome Work! I will review this in a couple days when I am not so sick

[lewysDavies]

Why can't we always use scope provided? Tests still pass fine?

[PiggyPiglet]

Why can't we always use scope provided? Tests still pass fine?

I wasn't able to run the tests when using the provided scope.

[portlek]

There is no need to test actually, because of the unit test :D build script should test all things. As a developer, we don't need to make real tests.

[PiggyPiglet]

There is no need to test actually, because of the unit test :D build script should test all things. As a developer, we don't need to make real tests.

I'm not sure you understand what we're talking about.

[lewysDavies]

Why can't we always use scope provided? Tests still pass fine?

I wasn't able to run the tests when using the provided scope.

Hmm strange, as I was able to (even with a full maven update). Did you build the project before running the tests? Documentation says it's used during the build & tests.

I am still debating if it's worth adding another dependency as that would end the simple copy & paste instalation. It's only a simple utility and I agree jetbrains annotations are far sexier and I use them in all my projects, however I wanted this to be pure Java 8.

[PiggyPiglet]

Why can't we always use scope provided? Tests still pass fine?

I wasn't able to run the tests when using the provided scope.

Hmm strange, as I was able to (even with a full maven update). Did you build the project before running the tests? Documentation says it's used during the build & tests.

I am still debating if it's worth adding another dependency as that would end the simple copy & paste instalation. It's only a simple utility and I agree jetbrains annotations are far sexier and I use them in all my projects, however I wanted this to be pure Java 8.

There's nothing impure about annotations. Anyway, while I appreciate your assistance in getting the tests working on my side, to do so is unnecessary, as it doesn't affect the validity of this pull request, considering they work fine on your end.