-
-
Notifications
You must be signed in to change notification settings - Fork 628
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
protobuf_gen breaks other goals if config flags are missing #456
Comments
This may just be the tip of the iceberg. I fixed the protobuf defaults and ran into some more. I'll get this target to compile and upload a patch. |
I also ran into a bunch: jvm, protobuf, ivy. Presumably we can do a much more stringent audit after the new options system lands. |
I am moving our defaults from pants.ini into default= arguments to fix it. I think that helps us meet the desired endgoal of an empty pants.ini, doesn't it? |
Yup! It's a good idea regardless. |
protobuf-gen now has some reasonable defaults as of commit 35d8a74. However, I'm pretty sure the Aurora project is not out of the woods:
Cannot satisfy requirements: [PythonRequirement(mesos==0.18.0)] I've asked for help in their IRC channel. |
We resolved that issue internally, assuming it was for the same reason. We ended up needing to force the |
protobuf_gen does not need settings in pants.ini any more. |
The text was updated successfully, but these errors were encountered: