Is your feature request related to a problem? Please describe.
The way interfaces work it's a bit unclear how you pass a parameter to a @MavenOption, when using @MavenCLIOptions. Current (0.13.1) documentation only shows examples without arguments.
Describe the solution you'd like
Improve documentation by adding an example with parameter as I think there are two solutions in general, but only the last is the best when using @MavenCLIOptions I think.
@MavenOption("-f pom.xml")
should result in the same as
@MavenOption(value = MavenCLIOptions.FILE, parameter = "pom.xml")
Describe alternatives you've considered
Leaving it as it be and blame the user to be stupid not knowing how to pass multiple parameters to a annotation. 🤷♂️
Additional context
Documentation as of now only shows examples where the @MavenCLIOptions does not need a parameter and therefor it's not needed to write the value parameter of the @MavenOption annotation explicit.
Is your feature request related to a problem? Please describe. The way interfaces work it's a bit unclear how you pass a parameter to a
@MavenOption
, when using@MavenCLIOptions
. Current (0.13.1) documentation only shows examples without arguments.Describe the solution you'd like Improve documentation by adding an example with parameter as I think there are two solutions in general, but only the last is the best when using
@MavenCLIOptions
I think.So full test could look like
Describe alternatives you've considered Leaving it as it be and blame the user to be stupid not knowing how to pass multiple parameters to a annotation. 🤷♂️
Additional context Documentation as of now only shows examples where the
@MavenCLIOptions
does not need a parameter and therefor it's not needed to write thevalue
parameter of the@MavenOption
annotation explicit.