Would it make sense to see to merge with https://www.mojohaus.org/license-maven-plugin/?

[batmat]

Describe your use-case which is not covered by existing documentation.

(Disclaimer: I haven't looked at the specific use cases handled by this plugin here, and the MojoHaus' eponym plugin.)

Have we considered contributing this plugin's features to https://www.mojohaus.org/license-maven-plugin/ and switch to the latter?

Why:

• doing Maven related work is more MojoHaus' scope than Jenkins'.
• There is a maven plugin out there with the very same name. Confusion ahead. And MojoHaus is much more widely used in the Maven ecosystem.

Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.

https://www.mojohaus.org/license-maven-plugin/

[batmat]

To be clear: I do not feel extremely strongly either way. I am leaning toward we should merge, but overall I'm more interested in having a reference place for our conscious decision on whether we go one way or another.