-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add back shade profile for shade removed in #12712 #12979
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #12979 +/- ##
============================================
+ Coverage 61.75% 62.18% +0.43%
+ Complexity 207 198 -9
============================================
Files 2436 2502 +66
Lines 133233 136503 +3270
Branches 20636 21128 +492
============================================
+ Hits 82274 84882 +2608
- Misses 44911 45349 +438
- Partials 6048 6272 +224
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
f70307d
to
c71f4b2
Compare
c71f4b2
to
5992270
Compare
cc: @jasperjiaguo |
<properties> | ||
<shade.phase.prop>package</shade.phase.prop> | ||
</properties> |
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.
nit: Isn't that the default phase? IICU we don't need to provide the phase.
So... IICU:
Is that correct? PS: I guess we can discuss this in another PR but... why do we need shade to be on by default? I think we should only shade drivers and some plugins and at least it should be pretty safe to only turn shade on in profile |
It's disabled by default. Plugins modules are enabled by default. |
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.
Having per module behavior and using different key to skip shading can be very confusing. Since we are bringing back the old behavior, we can merge it for now to fix the immediate issue.
Ideally, we should categorize the modules into different levels, and put all configs into root pom and use level to control how many modules to shade
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 for the fix
Per #12969, this PR add back the profiles removed in #12712 for backward compatibility for submodules:
Use profile default to control, can enable by adding flag
-Pbuild-shaded-jar
:Use property to control profile enable, default enabled, allow disable by adding flag
-DskipShade=true
Usage:
build-shaded-jar
, default is true or false