This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
Fix Maven build-time warnings #29
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
February 4, 2016 10:59
This removes the following warning when building or running tests with JDK 6: Feb 4, 2016 10:56:26 AM org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule WARNING: Module [groovy-all] - Unable to load extension class [org.codehaus.groovy.runtime.NioGroovyMethods]
This eliminates the following warnings during build:
[WARNING] The expression ${artifactId} is deprecated. Please use
${project.artifactId} instead.
[WARNING] The expression ${version} is deprecated. Please use
${project.version} instead.
|
LGTM! |
yacaovsnc
added a commit
that referenced
this pull request
Feb 4, 2016
Fix Maven build-time warnings
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There were a couple of warnings during a Maven build that I took care of; see the individual commits for details.
Manual testing
Set my
JAVA_HOMEto JDK1.6.0_20on Windows and ranmvn clean verify. There are no longer any warnings.Mission accomplished!