duplicate parameters in multiple mojos of one plugin
Just stumbled over this duplicate skip in the packaging plugin:
To my understanding that can happen if multiple mojos of the same plugin declare identical names for options, right? Should we fix this by always introducing an abstract super class when we notice such clashes? Or is there anything in the maven build process for plugins that can be enabled to check for such clashes? Or a unit test looking at the parameters via reflection, some maven model utility etc.
I think this issue is more something to report to leminx-maven.
I think @mickaelistria is right and this is a leminx-mven issue I'm not aware that it is required for mojos to use distinct parameter names or extend a common class.
If you try the above example on your local machine, then you would notice that the 2 skip options have different documentation being shown on the right (not visible in the screenshot), because those really are 2 entirely different options. How would the leminx plugin decide which one to show? I'm still in favor of avoiding this in the tycho plugin code instead.
leminx should at least show that they are belong to different mojos then, I don't think this can be handled by Tycho especially if
because those really are 2 entirely different options
Having a baseclass only to share a single parameter that has different meanings do not sound like it solves anything.