[
https://issues.apache.org/jira/browse/SUREFIRE-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496079#comment-17496079
]
Tibor Digana edited comment on SUREFIRE-2000 at 2/22/22, 1:24 PM:
------------------------------------------------------------------
[~sjaranowski]
I do not remember the repro steps after long time. I think I saw this problem
with the classpath in a traditional provider, see the integration test
{{Surefire943ReportContentIT#test_parallelBoth()}}. If you run the IT project
with {{mvn -X}} you will see the surefire forked Jar kept on the file system
which can analyzed more further.
was (Author: tibor17):
[~sjaranowski]
I do not remember the repro steps after long time. I think I saw this problem
with the classpath in a traditional provider, see the integration test
{{Surefire943ReportContentIT#test_parallelBoth()}}. If you run the IT project
with {{mvn -X}} you will see the surefire forked Jar which can analyzed further.
> Classpath contains redundant JAR artifacts if ShadeFire provider is active
> --------------------------------------------------------------------------
>
> Key: SUREFIRE-2000
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2000
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin,
> surefire-shadefire
> Affects Versions: 3.0.0-M5
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 3.0.0-M6
>
>
> There are extra more artifacts than necessary on the classpath if ShadeFire
> provider is used. This may cause new conflicts if testing Surefire itself.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
