[
https://issues.apache.org/jira/browse/SUREFIRE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074091#comment-17074091
]
Tibor Digana commented on SUREFIRE-1768:
----------------------------------------
[~rolaca11]
wow, so this looks like a JVM issue.
If you have {{module-info}} in src/main and if you do not have {{module-info}}
in src/test then the {{classes}} directory appear on the module path and the
tests appear on the class path.
[~rfscholte]
Do you have experiences with the behavior of resources in Java Module System?
Could this be a bug in JVM?
> 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)
