-
Notifications
You must be signed in to change notification settings - Fork 153
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
Support passing toolHome to Maven/Buck/Bazel invoker #252
Conversation
ade0fdc
to
dee7b20
Compare
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 think we should add a separate base class for the (Maven|Bazel)ScenarioDefinition
and the (Maven|Bazel)ScenarioInvoker
. Then we can move the shared code from ScenarioInvoker
there, instead of leaving the code in ScenarioInvoker
and not using it in GradleScenarioInvoker
.
@blindpirate There are quite some changes regarding the invokers going on in #253, I think we should hold off with this PR until #253 has been merged. |
@blindpirate #253 has been merged, so we can go forward with this change. |
So that they can be invoked programmatically more easily.
dee7b20
to
33df461
Compare
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.
Nice work! I left two more comments.
src/main/java/org/gradle/profiler/BuildToolCommandLineScenarioDefinition.java
Show resolved
Hide resolved
8fdcaa2
to
3a388c3
Compare
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.
LGTM! Can you add the new scenario field to the documentation? Maybe as part of the Maven, Bazel, Buck examples?
Thanks @wolfs ! sure I will. |
So that they can be invoked programmatically more easily.
Fixes #245