default should probably be to show deprecated but not non-functioning

what is normal? all?

stuff that isn’t deprecated

i just mean that an option can be in one of three states

oh i see what you mean

this option option should probably account for that (even if you don't implement handling for deprecated)

there’s deprecation version in the context, so i can tell the state

perfect.

Do we need an option for this? Why not always exclude “non-functioning” options?

yeah I think that’s the plan

okay. i’ll just set it as default behavior

any suggestions on how to write the test for it? using the existing deprecated options would be time sensitive

is there a fake/mock task to add some fake options to?

seems likely there are already tests that register fake tasks

I remember someone was going to publish a document about how they set up remote cache for pants. Did I miss it or has it not happened yet?

mike.cripps: using

.pants.d/test/junit/*.xml

worked beautifully -- thanks

To test the pants options whether prints out only functioning options, I tried to make a dummy task to contain some dummy deprecated options. but so far had some trouble loading up the task as a plugin.

load_build_configuration_from_source(build_configuration, additional_backends=backends or [])
  File "/Users/yic/workspace/pants/src/python/pants/bin/extension_loader.py", line 124, in load_build_configuration_from_source
    load_backend(build_configuration, backend_package)
  File "/Users/yic/workspace/pants/src/python/pants/bin/extension_loader.py", line 142, in load_backend
    .format(backend=backend_module, error=e))

Exception message: Failed to load the pants.contrib.dummy_options.register backend: No module named dummy_options.register

even if the structures looks like this

[tw-mbp-yic pants (option_option)]$ find contrib/dummy_options/src/python/pants/contrib/dummy_options/
contrib/dummy_options/src/python/pants/contrib/dummy_options/
contrib/dummy_options/src/python/pants/contrib/dummy_options//__init__.py
contrib/dummy_options/src/python/pants/contrib/dummy_options//BUILD
contrib/dummy_options/src/python/pants/contrib/dummy_options//register.py
contrib/dummy_options/src/python/pants/contrib/dummy_options//tasks
contrib/dummy_options/src/python/pants/contrib/dummy_options//tasks/__init__.py
contrib/dummy_options/src/python/pants/contrib/dummy_options//tasks/BUILD
contrib/dummy_options/src/python/pants/contrib/dummy_options//tasks/dummy_options.py

posted on https://rbcommons.com/s/twitter/r/3455, not sure what I am missing to load the plugin

I don’t think contrib is the right place for dummy options for use in tests

contrib is for experimental language support and so on, things that other repos might need

There are ways to register options programmatically in tests

@wide-energy-11069: you need to add a line to the python path settings in pants.ini

currently pants options tests are only done via pants_run, tests/python/pants_test/option/test_options_integration.py

what about examples?

instead of contrib

the regular option test are covered by unit test, but options goal is a console task, which could be a bit tricky

@limited-country-20626: thanks. got it working

with the plugin

now the question is where should i put it?

maybe pants-plugins