[ https://issues.apache.org/jira/browse/SUREFIRE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074422#comment-17074422 ]
Robert Scholte commented on SUREFIRE-1768: ------------------------------------------ This is new and unexpected to me. I'll put it on the mailinglist first to see if we might have misunderstood a detail. If not, I can register an issue for it. btw. I noticed a very small difference between the 2 URLs: one ends with a / > 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)