Updated .travis.yml to force the use of Ant over Gradle#34
Merged
Conversation
- The custom install script prevents Travis' auto-detection of the build tool. - `install: ant <target>` forces the use of ant even if a build.grade file is detected.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description of the Change
The default WorldWindJava build process uses Apache Ant. This change to the Travis configuration ensures that
antis used even if Gradle or Maven build configuration files are detected by Travis-CI.Why Should This Be In Core?
This change ensures the prescribed build process is followed.
Benefits
Without this change, Gradle or Maven could be used by Travis instead of
ant.Potential Drawbacks
None.
Applicable Issues
PR #30
Issue #11