jasig / maven-notice-plugin Goto Github PK

I'm using this plugin with Maven 3.5.0 and JDK 11 and I'm getting this error:

[ERROR] Failed to execute goal <my-plugin>:generate-files (default) on project webapp: Unable to execute mojo: Failed to parse 'license-mappings.xml' from 'jar:file:/home/slave/.m2/repository/<package>/license-resources/2.0-SNAPSHOT/license-resources-2.0-SNAPSHOT.jar!/license-mappings.xml': unexpected element (uri:"https://source.jasig.org/schemas/maven-notice-plugin/license-lookup", local:"license-lookup"). Expected elements are <{}license-lookup> -> [Help 1]

The error only happens on my Jenkins workers, while on my local machine everything runs fine. Can you help me understand the issue?

The license-mappings.xml is well formed and has been in use for the last 3 years so there is no issue with it, the last commit on it is from the start of 2020 and in more than a year we never had an issue before.

Seems that the plugin requires javax.xml.bind package that is not a part of default distribution anymore

Per https://github.com/Jasig/maven-notice-plugin/releases, the latest appears to be 2.0.0, but this version is not (yet) found in Maven Central.

https://repo1.maven.org/maven2/org/jasig/maven/maven-notice-plugin/

[ERROR] Plugin org.jasig.maven:maven-notice-plugin:2.0.0 or one of its dependencies could not be resolved: Could not find artifact org.jasig.maven:maven-notice-plugin:jar:2.0.0 in central (https://repo.maven.apache.org/maven2) -> [Help 1]

This plugin's name conflicts with the maven plugin naming convention.

Calling it maven-<yourplugin>-plugin (note "Maven" is at the beginning of the plugin name) is strongly discouraged since it's a reserved naming pattern for official Apache Maven plugins maintained by the Apache Maven team with groupId org.apache.maven.plugins. Using this naming pattern is an infringement of the Apache Maven Trademark.

As far as I can see a compliant name would be notice-maven-plugin.