Not fail if java plugin doesn't in pom.xml #295
Merged
Conversation
This file contains hidden or 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
johnttompkins
approved these changes
Aug 11, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Issue #, if available: #282
Description of changes:
As described in #282, the java plugin could be configured somewhere else other than the pom.xml under the resource handler directory.
The tool was trying to help the runtime dependency compatibility check, but it should not have assumption on how to build the package as there are various ways to build the package.
This PR will loose the java plugin version check in pom.xml. If the java plugin dependency doesn't find, don't fail the
generate.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.