Exclude *.java from being added to library jars #992
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
osana
force-pushed
the
osana-remove-from-jar
branch
from
ad62f4e
to
0a4d1f8
Compare
|
An easy way to check that there are no java classes is to list jar content.
|
LukasPaczos
approved these changes
Apr 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Mapbox java sdk uses AutoValue library to generate boilerplate code for value setters / getters and to generate
equals,hashCodeandtoStringmethods.It is a useful tool. However, it was reported that generated
.javafiles end up in the library jars. This is undersirable. This PR excludes.javafiles from being added to the library jars.closes #989