[
https://issues.apache.org/jira/browse/SUREFIRE-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503320#comment-17503320
]
Christopher Tubbs commented on SUREFIRE-2035:
---------------------------------------------
I even tried explicitly adding the main jar artifact onto the class path using
{{additionalClasspathElements}}, but that didn't work. The jar was still
missing when I printed {{System.getProperty("java.class.path")}}
> Main artifact jar not present on test class path for tests
> ----------------------------------------------------------
>
> Key: SUREFIRE-2035
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2035
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
> Affects Versions: 3.0.0-M5
> Reporter: Christopher Tubbs
> Priority: Critical
>
> While trying to troubleshoot https://github.com/apache/accumulo/issues/2555,
> I noticed that there was a behavior change between 3.0.0-M4 and 3.0.0-M5 that
> causes the main artifact jar to be missing from the class path in test cases.
> I was able to verify that by printing out
> {{System.getProperty("java.class.path")}} before and after switching to M5,
> and confirmed that the jar was missing after switching.
> For some reason, tests still seem to work okay, though I can't figure out
> why. However, if I try to launch a process using Java's ProcessBuilder using
> the same class path from {{System.getProperty("java.class.path")}}, that
> process fails with ClassNotFoundException, failing to find classes that
> should definitely be present on the class path from the main artifact.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
