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.
Packaging tools jar with the python package #1634
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packaging tools jar with the python package #1634
Changes from 11 commits
7385caf
3874af5
39216a9
ec032bb
2466599
ee24ee3
3efc7ea
f5c54b7
104d18a
34bdfd8
1b740a1
0dc45a7
b048fa4
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to pass arguments to the build_jar function.
This probably should come from
build.sh
so that we can have different builds for different jobs.For example, in #1639 I added a profile-id
release
. We should be pass that argument down to the mvn command in order to create the specific build we need.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @amahussein . I am evaluating the final behavior of this script on the basis of the internal build jobs and post having finalised the design, will update the build.sh file to take appropriate params.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the name
fetch_all_csp
is not good in that option. If this is a flag indicatingFat mode
, then why don't we use something more descriptive likefat_mode_enabled
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will update the comments to make this more clear. So previous behavior was -
For this
./build.sh fat
vs./build.sh
triggered either casesNow to replicate the same, script calling behavior , we still call either
./build.sh fat
and./build.sh
. The difference now, fat mode packs all the csp related dependencies by compressing it into a tgz file and includes it in the resources.fetch_all_csp
flag is for the internal prepackage_mgr to include the jar or the jar/csp resources. Hence --fetch_all_csp
as a param.Let me know if this still seems wrong, will update it in that case
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did not get the new behavior.
for both build options (fat and non-fat), do the tools-jar go into
tools-resources
or it depends on the build mode?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For both build modes, the tools-jar goes into the resources.
In the fat mode is that all csp dependencies are also packed with the jar.