-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JUnit dependency should be excluded #104
Comments
@dsyer Are you sure that they're brought in by the Kafka binder? Neither JUnit nor JLine are dependencies of it (it's easy to prove that with an Initializr generated app, which I just did, locally). |
<dependencies>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-test</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-stream-binder-kafka</artifactId>
</dependency>
</dependencies>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-dependencies</artifactId>
<version>Camden.BUILD-SNAPSHOT</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
|
I stand corrected on JLine - it is brought in by ZK (which we need - I guess we can exclude JLine in particular. It would be much simpler if you just excluded JUnit, which the original issue was about, is a rather odd story there:
Oddly enough, the change of scope of JUnit (from However, if only So we need to find out what changes the scope of JUnit in this scenario. |
It's jline that brings in junit in compile scope:
(and that comes in with just the binder). |
@dsyer thanks :) and that happens only for version |
Possibly some others (jline?). There are some really funky things on the classpath of a SCS Kafka app.
The text was updated successfully, but these errors were encountered: