-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: FIS 2.0-patches
-
Component/s: None
-
Labels:None
-
Epic Link:
The shrinkwrap jars should only be in the test scope. But they end up in the generated SB application jar:
$ jar -tvf target/test-1.0-SNAPSHOT.jar | grep shrink
|
53055 Wed Feb 10 15:24:48 EST 2016 BOOT-INF/lib/shrinkwrap-resolver-api-maven-2.2.2.jar
|
18048 Wed Feb 10 15:24:26 EST 2016 BOOT-INF/lib/shrinkwrap-resolver-spi-2.2.2.jar
|
65871 Sat Oct 24 22:27:14 EDT 2015 BOOT-INF/lib/shrinkwrap-api-1.2.3.jar
|
21563 Wed Feb 10 15:24:18 EST 2016 BOOT-INF/lib/shrinkwrap-resolver-api-2.2.2.jar
|
5838 Wed Feb 10 15:26:52 EST 2016 BOOT-INF/lib/shrinkwrap-resolver-spi-maven-archive-2.2.2.jar
|
It seems the mvn dependency:tree does indeed list them as being in the runtime scope:
$ mvn dependency:tree | grep shrink
|
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1G; support was removed in 8.0
|
[INFO] | | \- org.jboss.shrinkwrap:shrinkwrap-api:jar:1.2.3:runtime
|
[INFO] | | \- org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-spi:jar:2.0.0-alpha-8:test
|
[INFO] | \- org.jboss.shrinkwrap:shrinkwrap-impl-base:jar:1.2.3:test
|
[INFO] | \- org.jboss.shrinkwrap:shrinkwrap-spi:jar:1.2.3:test
|
[INFO] | \- org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-api-base:jar:2.0.0-alpha-8:test
|
[INFO] +- org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-depchain:pom:2.2.2:test
|
[INFO] | +- org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api:jar:2.2.2:runtime
|
[INFO] | +- org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-spi:jar:2.2.2:runtime
|
[INFO] | +- org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven:jar:2.2.2:runtime
|
[INFO] | +- org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-spi-maven:jar:2.2.2:test
|
[INFO] | +- org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-api-maven-archive:jar:2.2.2:test
|
[INFO] | +- org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven:jar:2.2.2:test
|
[INFO] | \- org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven-archive:jar:2.2.2:test
|
[INFO] | +- org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-spi-maven-archive:jar:2.2.2:runtime
|
I peeked at the fabric8-project-bom-camel-spring-boot bom and noticed. Entries like:
<dependency>
|
<groupId>org.jboss.shrinkwrap.resolver</groupId>
|
<artifactId>shrinkwrap-resolver-spi-maven-archive</artifactId>
|
<version>${version.org.jboss.shrinkwrap.resolver.shrinkwrap-resolver-spi-maven-archive}</version>
|
<scope>runtime</scope>
|
</dependency>
|
Could this be why they are in the runtime scope?
