It could be done the way you suggested as well. I selected the open-ended option to allow the plugin to work across many versions of Buckminster. Old versions won't support the ant logging and that would require the UI to be much smarter, hiding and showing components based on the version of Buckminster. The open-ended option is more error-prone for users who might not know the syntax of the options, but it makes the plugin less dependent on the version of Buckminster it is calling, which is a good trade-off in my opinion. We may want to go even further and just provide a "Buckminster Options" field that allows for free-form options to be sent to Buckminster in the future.