Never mind, I think I figured this out. I had two "parent" artifacts with
similar names, and I ran the build in the wrong one. It's still a bit
confusing where the exclusion has to go, but I now have a single exclusion
for junit-platform-runner, in the parent pom, so I don't have to do this in
Ok, so the tree has output like this:
--
[INFO] +- com.att.idp:idp-seed-sdk-core:jar:2.7.0-SNAPSHOT:compile
[INFO] | +- org.junit.jupiter:junit-jupiter-api:jar:5.8.2:compile
[INFO] | | +- org.opentest4j:opentest4j:jar:1.2.0:compile
[INFO] | | \-
Import scope only sets versions of dependency - not add it to dependency.
Please examine output of dependency:tree and look where is added
junit-platform-runner
pt., 17 cze 2022 o 20:47 David Karr napisał(a):
> Ok, what is the proper way to do that, considering I have the following in
> a bom
Ok, what is the proper way to do that, considering I have the following in
a bom imported by my parent pom:
org.junit
junit-bom
import
pom
5.8.2
Do you have on your classpath - junit-platform-runner?
Please remove it.
pt., 17 cze 2022 o 20:23 David Karr napisał(a):
> I'm posting a new note, as this might be a different issue.
>
> I recently got good advice on this list about how to properly specify the
> version overrides for the
I'm posting a new note, as this might be a different issue.
I recently got good advice on this list about how to properly specify the
version overrides for the junit-bom artifacts. When I implemented that, I
saw that I was consistently getting the correct versions for those
artifacts.
However,
Hi,
On 17.06.22 02:27, David Karr wrote:
Sorry, can you clarify exactly what you mean by that?
Usually you have something in your pom file to use the spring boot
dependencies:
org.springframework.boot
spring-boot-dependencies
