[
https://issues.apache.org/jira/browse/SUREFIRE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080046#comment-17080046
]
László Stahorszki commented on SUREFIRE-1768:
---------------------------------------------
[~rfscholte]
Sorry for bothering you more with this, but even though the above phenomenon is
by design, I still feel like this is something to be worked around. I keep
finding more and more cases where the fact that the test module is patched into
the main module causes all kinds of classpath searching problems.
One of which was the original issue with Spring Data repositories being
undetectable.
My first idea is not to have the test module patched into the source module,
instead, let it be its own module. I believe that this way, the developer has
more control and makes the overall experience a little less "magic" in the
background, albeit it will require a little bit more configuration.
What do you think?
> 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
> Assignee: Robert Scholte
> 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)
