Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
When the shadeTestJar option is enabled it tries to fetch the test jars from all dependencies and include them in the shaded artifact.
For every dependency, and every available repository, there is a download attempt that fails most of the time (since most dependencies do not publish the test artifacts).
Downloading from confluent: https://packages.confluent.io/maven/com/sun/jersey/contribs/jersey-guice/1.19.4/jersey-guice-1.19.4-tests.jar Downloading from central: https://repo.maven.apache.org/maven2/com/sun/jersey/contribs/jersey-guice/1.19.4/jersey-guice-1.19.4-tests.jar Downloading from repository-release: https://repository.apache.org/content/repositories/releases/com/sun/jersey/contribs/jersey-guice/1.19.4/jersey-guice-1.19.4-tests.jar Downloading from shibboleth: https://build.shibboleth.net/nexus/content/groups/public/com/sun/jersey/contribs/jersey-guice/1.19.4/jersey-guice-1.19.4-tests.jar [WARNING] Could not get tests for com.sun.jersey.contribs:jersey-guice:jar:1.19.4:compile
All these download attempts increase build time noticeably, especially on slow internet connections.
Shading the test jars in Kafka module is not necessary since we are not using the resulting jars (kafka-handler-4.1.0-SNAPSHOT-tests.jar) anywhere inside the project (no occurrence of kafka-handler along with tests).
Attachments
Attachments
Issue Links
- links to