[license-gather-plugin] Ability to handle multiple licensed artefacts about vlsi-release-plugins HOT 1 OPEN

Does #50 (comment) cover your case?

Frankly speaking, there's no way to automatically resolve cases when the developer list multiple licenses.

It would be awesome if they used SPDX license expression in Bundle-License, however, they rarely do so,
In the non-tirival cases, I do the following:
a) Approach projects to update their MANIFEST, pom.xml, etc. For instance, here's the list of issues I created when adding license verification to JMeter: apache/jmeter#469 (comment)

b) Use overrideLicense to clarify the actual meaning. For instance, it detected EPL-2.0 AND GPL2 w/ CPE, and most likely the actual license is EPL-2.0 OR GPL2-or-later with Classpath-Exception. If that is the case, you could add the relevant override.

I might start collecting a set of well-known resolution cases (e.g. I have resolution history in JMeter: https://github.com/apache/jmeter/blob/da6efde33eb80751eff1f778d63b67e4f9bcd652/src/licenses/build.gradle.kts#L72 )
However, I have not explored that yet.

from vlsi-release-plugins.