General:
Additional:
It's necessary to add the following lines to the section configuration of the described artifact classpath-maven-plugin:
<configuration> ... <path>lib/*.jar</path> <isMask>true</isMask> ... </configuration>
In addition to the parameters described in the previous question, you must add withSubDir = true parameter to the section configuration of the described artifact classpath-maven-plugin:
<configuration> ... <path>lib/*.jar</path> <isMask>true</isMask> <withSubDir>false</withSubDir> ... </configuration>
In the described plugin it is possible to manage such collisions as a overlap of jar-libraries already connected via dependency with libraries connected via the classpath-maven-plugin. The overlapDependencyMatch parameter in the section configuration is responsible for this:
<configuration> ... <overlapDependencyMatch>true</overlapDependencyMatch> ... </configuration>
In the described plugin it is possible to not override the classpath of your project directly, but write the resulting classpath-string to the file or project variable (with subsequent access to it via ${variableName}). For this the assignProjectClasspath parameter is set to false, and adding the following output parameters for writing classpath-string:
<configuration> ... <assignProjectClasspath>false</assignProjectClasspath> <outputFile>${project.build.directory}/classpath.txt</outputFile> <outputProperty>variableName</outputProperty> ... </configuration>
Error output with stopping further plugin execution in the absence of found jar-libraries for a single input configuration parameter path is specified in the section configuration with the parameter errorIsEmptyPath = true:
<configuration> ... <errorIsEmptyPath>true</errorIsEmptyPath> ... </configuration>