maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From László Stahorszki (Jira) <j...@apache.org>
Subject [jira] [Comment Edited] (SUREFIRE-1768) Main classes not included in classpath when using Java Modules
Date Fri, 03 Apr 2020 16:09:00 GMT

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

László Stahorszki edited comment on SUREFIRE-1768 at 4/3/20, 4:08 PM:
----------------------------------------------------------------------

[~rfscholte]

Could you please clarify some things for me:
 # What patch overrides what? I'm sorry, I don't understand.
 # Those snippets help me find resources in given modules as opposed to just on the plain
classpath?
 # If 2) is true. Is it designed like this to enforce the encapsulation the module system
was designed for?

Thanks in advance


was (Author: rolaca11):
[~rfscholte]

Could you please clarify some things for me:
 # What path overrides what? I'm sorry, I don't understand.
 # Those snippets help me find resources in given modules as opposed to just on the plain
classpath?
 # If 2) is true. Is it designed like this to enforce the encapsulation the module system
was designed for?

Thanks in advance

> 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)

Mime
View raw message