-
Notifications
You must be signed in to change notification settings - Fork 168
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
OkBuck is executing Dagger on tests even if it wasn't told to do so #360
Comments
Definitely not by intelligent design, but more of a simplification made in the early days. This needs to be refactored to work like any other compile time dependency config by taking main/test/flavor/buildtype conventions into account |
I think this might break
|
Yep. I'm in the process of untangling the dependencies and make them better isolated :) |
@kageiit I'm still getting the above error ( |
Hmm. Would be great to get some repro steps at this point. |
Since I'm using Java 8 in my unit tests I needed to add the Go to After this you should be able to run your unit tests. |
This time with repro - https://github.com/vanniktech/okbuck-playground/pull/5
Is this by design?
The text was updated successfully, but these errors were encountered: