<https://github.com/pantsbuild/pants/issues/9149>
# general
f
a
on a separate but related note, do you think jvm options for any tool (junit and other) and/or the platform/distribution selection might be something that's worth adding a
CompilerOptionSetMixin
to?
enables setting up a dictionary in pants.ini which allows targets to selectively turn on and off sets of command-line options in a hygeinic way
+ i can offer to implement this entirely if it would help you
it would be a single small PR
f
hm. that does seem useful. I’d need to think about it a little further.
a
yes!
just a thought
f
I feel like there’s a potential for a more consistent, sophisticated approach to jvm_options in general
since there’s multiple sources of them and they should have a strict, consistent ordering
eg, global+platform+task specific+target specific+cli-flags or something
a
that is definitely what MirroredTargetOptionMixin and CompilerOptionSetsMixin are exactly created to do
f
nice
a
like exactly that
it has a specific precedence ordering that i believe aligns exactly with your message
f
nice
For MirroredTargetOptionMixin, it’d be cool if it could use the same parsing infra as options. I’m not sure how to do that though — and don’t have time
a
oh, that's super super interesting
do you have time to make an issue about what you're thinking?
i would love to hear it