You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christopher Tubbs (Jira)" <ji...@apache.org> on 2022/04/04 17:17:00 UTC

[jira] [Updated] (SUREFIRE-2035) Main artifact jar not present on test class path for tests

     [ https://issues.apache.org/jira/browse/SUREFIRE-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs updated SUREFIRE-2035:
----------------------------------------
    Attachment: surefire-2035-example-main.zip

> 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
>         Attachments: surefire-2035-example-main.zip
>
>
> 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, unit 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)