not resolved, but avoid the problem:
org.apache.maven.plugins
maven-jar-plugin
3.1.0
default-jar
package
repository
true
/${settings.localRepository}/
${it.main}
. ..
must run "mvn install" in parent level, that will cause problem.
eg:
integration tests
springmvc-tests
springmvc-tests-general-with-springboot
run in " integration tests" or " springmvc-tests", have problems.
but run in " springmvc-tests-general-with-springboot", no problem.
2018-07-29 2:4
infact classpath data in MANIFEST.MF is no problem, "java -jar xx.jar" is
no problem.
just only classpath for "mvn install" have problem, exclude is not
a solution for this.
2018-07-28 14:40 GMT+08:00 Willem Jiang :
> It looks like the plugin add all the m2 depedencies into the classpath.
> Can
It looks like the plugin add all the m2 depedencies into the classpath.
Can you exclude them[1] in the maven jar plugin ?
[1]
https://maven.apache.org/plugins/maven-jar-plugin/examples/include-exclude.html
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Sat, Jul 28, 2018 at 9:33 AM, wjm
sorry, description is not correct
green lines is the key information, that's for run by "java -jar xxx.jar",
but it cause "mvn install" failed.
org.apache.maven.plugins
maven-jar-plugin
3.1.0
assembly
package
${root.dir}/integration-tests/target/${project
1.there is no problem run unit test, and start spring applicationContext,
by "mvn install"
2.add maven-jar-plugin in pom, set outputDirectory, and run "mvn install"
again
spring will load duplicated libraries in different directory, that cause
spring start failed.
(target/lib is my " outputDirector
