-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Moved versioning plugin to the root only. #174
Conversation
versioning still resolvable by sub-projects, but evaluating the info only once. As the evaluation is happened on the configuration time, this change speeds up the configuration time with a few seconds (4-7 for me). The evaluation of that info also has been pushed into the execution phase, at least for the jar task.
Review status: 0 of 2 files reviewed at latest revision, 2 unresolved discussions, some commit checks broke. build.gradle, line 54 at r1 (raw file):
this change applies the gradle/publish.gradle, line 93 at r1 (raw file):
I suppose moving the calculation of manifest entries to execution time does make the build faster, as it only happens if the Comments from Reviewable |
Reviewed 2 of 2 files at r1. Comments from Reviewable |
(Just for correctness:) Well putting the manifest into doFirst is not only speeds up the build when the Before this change it was executed regardless the |
Agreed. I think the |
Reverted the publish -> root project movement of the versioning plugin. |
Your original PR made me think that it makes better sense to calculate the GIT hash once, same thing with other on-the-fly values. This means moving the |
Moved versioning plugin to the root only making versioning still resolvable by sub-projects, but evaluating the info only once. As the evaluation is happened on the configuration time,
this change speeds up the configuration time with a few seconds (4-7 for me).
The evaluation of that info also has been pushed into the execution
phase, at least for the jar task.
This change is