You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (Jira)" <ji...@apache.org> on 2020/04/03 09:49:00 UTC

[jira] [Comment Edited] (SUREFIRE-1768) Main classes not included in classpath when using Java Modules

    [ https://issues.apache.org/jira/browse/SUREFIRE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074444#comment-17074444 ] 

Tibor Digana edited comment on SUREFIRE-1768 at 4/3/20, 9:48 AM:
-----------------------------------------------------------------

[~rolaca11]
As [~rfscholte] said he will put this issue on the mailing list. Please *subscribe* to the [mailing list|https://maven.apache.org/mailing-lists.html] and find the discussion there.
This is the open mailing list for developers and users:
https://lists.apache.org/list.html?dev@maven.apache.org
https://lists.apache.org/list.html?users@maven.apache.org


was (Author: tibor17):
[~rolaca11]
As [~rfscholte] said he will put this issue on the mailing list. Please *subscribe *to the [mailing list|https://maven.apache.org/mailing-lists.html] and find the discussion there.
This is the open mailing list for developers and users:
https://lists.apache.org/list.html?dev@maven.apache.org
https://lists.apache.org/list.html?users@maven.apache.org

> Main classes not included in classpath when using Java Modules
> --------------------------------------------------------------
>
>                 Key: SUREFIRE-1768
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1768
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: classloading
>    Affects Versions: 3.0.0-M4
>         Environment: Windows 10, JDK 11
>            Reporter: László Stahorszki
>            Priority: Major
>
> According to the [documentation|http://maven.apache.org/surefire/maven-surefire-plugin/examples/configuring-classpath.html], the `classes` directory should be put on the classpath by default.
> In this case, given that I have a `demo` package in both my main sources and my test source, the enumeration `classLoader.getResources({color:#6a8759}"demo"{color})` should have 2 URLs in it. One for the package in the test sources and one for the main sources.
> When using the Java Module System, this is not the case. Instead, I get two URLs, both for the test sources. This error does not occur when not using the module system.
> I created a repository, which can reproduce this error. It can be found [here|https://github.com/rolaca11/test-classpath-demo]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)