Skip to content

Fix compiler warnings#424

Open
robert-s-ubi wants to merge 14 commits intomasterfrom
fix_compiler_warnings
Open

Fix compiler warnings#424
robert-s-ubi wants to merge 14 commits intomasterfrom
fix_compiler_warnings

Conversation

@robert-s-ubi
Copy link
Contributor

The legacy code produced a number of compiler warnings when building,
which might distract from actual issues being introduced.

Enable all recommended warnings when building and address all compiler
warnings, mostly with a real fix, and suppress warnings in select cases
where a fix is not feasible, so that the library compiles without any
warnings.

Add the Java compiler option to enable the recommended compiler warnings
to the gradle and maven builds.
The test classes in ocpp-v1_6-test rely heavily on using deprecated
constructors and unchecked type casts, so suppress the warnings.
Some ocpp-v1_6 tests rely heavily on the deprecated no-arg constructors,
so just suppress the deprecation warnings for them.
The ChangeAvailabilityConfirmation() constructor was marked deprecated
in the Javadoc, but missing the annotation.

Add the missing annotation.
@robert-s-ubi
Copy link
Contributor Author

@TVolden could you maybe spare some time to look over this PR as well? This is a "cleanup" PR to fix the annoying compiler warnings that were shown on every build.

Copy link
Member

@TVolden TVolden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks good. Good job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants