Use new ezbake methods for managing BC FIPS jars #196
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
The method we were using before was very hacky, taking advantage of this project copying stuff from resources/ext/build-scripts into the staging dir and using the vox:build Rake task to put things in the right place. This uses the changes in the latest ezbake to do the same procedure, pulling BC jars from the classpath and Maven cache, but letting ezbake handle it instead of hacking it in.
nmburgan
force-pushed
the
classpath_jars
branch
from
460e758 to
fe67c7b
Compare
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.
The method we were using before was very hacky, taking advantage of this project copying stuff from resources/ext/build-scripts into the staging dir and using the vox:build Rake task to put things in the right place. This uses the changes in the latest ezbake to do the same procedure, pulling BC jars from the classpath and Maven cache, but letting ezbake handle it instead of hacking it in.
Requires OpenVoxProject/ezbake#78 and a new ezbake release.