Missing license information for wrapped.com.vladsch.flexmark plug-ins

[trancexpress]

We are integrating eclipse.jdt.ls in our Eclipse based product, while reviewing added bundles we noticed that "wrapped" bundles (e.g. wrapped.com.vladsch.flexmark.*) have no about.html or other types of license information.

When checking the latest vscode-java release (https://github.com/redhat-developer/vscode-java/releases/download/v1.54.0/vscode-java-1.54.0-923.vsix) I do see those bundles included in the extension/server/plugins directory. But I find no mention of the license file in the packaged extension.

I assume the code comes from here: https://github.com/vsch/flexmark-java

With the license being BSD 2-clause, mandating that the copyright notice must be included: https://github.com/vsch/flexmark-java/blob/master/LICENSE.txt

The concatenated licenses under extension/dist also have no mention that I find. Aside from those, I find only the EPL 2.0 license. Am I missing the license infos due to not looking somewhere in the packaged extension?

If the license files are missing, is there a way to include them ahead of changes made to eclipse.jdt.ls? Maybe some flag, or property or tag here?

		<location includeDependencyDepth="infinite" includeDependencyScopes="compile" includeSource="true" label="3rd party" missingManifest="generate" type="Maven">
			<dependencies>
				<dependency>
					<groupId>com.vladsch.flexmark</groupId>
					<artifactId>flexmark-html2md-converter</artifactId>
					<version>0.64.8</version>
					<type>jar</type>
				</dependency>

I believe the same applies for org.objectweb.asm, the plug-ins don't include an about.html mentioning the license text (BSD 3-clause). And potentially the same applies for the JetBrains decompiler.

I'm opening an issue here instead of at https://github.com/redhat-developer/vscode-java, since I assume vscode-java is just running the mvn build from this repository and including the result.

[trancexpress]

Asked also on tycho, about what is needed in the target file: eclipse-tycho/tycho#5992

Seems that this shouldn't be done automatically by tycho, as it carries risks of adding wrong license information.