The irony is that it is not even possible to build a .JAR to remove some of the dependencies that the host is complaining about, even with the most recent version of AMPS that isn’t documented.
Using plugin SDK 8.2.7 + the seemingly-latest AMPS 8.12.0, there is a hardcoded list inside the amps-maven-plugin JAR (in class com.atlassian.maven.plugins.amps.BannedDependencies) of packages that you are not allowed to bundle, which include…the things that Confluence is now warning us we should bundle.
For example, Confluence says this:
2023-11-27 14:18:09,417 WARN [UpmAsynchronousTaskManager:thread-4] [osgi.hook.dmz.DmzResolverHook] filterMatches
Package org.apache.commons.lang3 is deprecated and will be made unavailable for export to plugin <PLUGIN> in a future release
But if you try to actually bundle it, Maven gives up this error:
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message:
make sure platform artifacts are not bundled into plugin
Found Banned Dependency: org.apache.commons:commons-lang3:jar:3.12.0
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
Perhaps someone could also look into fixing the tooling?