[
https://issues.apache.org/jira/browse/SUREFIRE-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146847#comment-17146847
]
Christian Stein commented on SUREFIRE-1811:
-------------------------------------------
_"By Three They Come."_
But, the default single Maven module directory structure and the underlying
(project object) model and most 3rd-party tools (especially IDEs) don't support
that Java module-centric way of thinking. After years of experimenting, I use
the following structures today.
I) Single Maven Module Project with Java Module named "com.greetings"
* main/java/module-info.java (with module com.greetings {})
* test/java/module-info.test (avoid same-name clashes) and resort to the
superpowers of the command line
II) Multi-Module Maven Project with Java Modules named "com.greetings" and "it"
"com.greetings"
* main/java/module-info.java (with module com.greetings {})
* test/java/module-info.test (avoid same-name clashes) and resort to the
superpowers of the command line
"it"
* test/java/module-info.java (with module it \{ requires com.greetings; })
> Add resources to JPMS test module
> ---------------------------------
>
> Key: SUREFIRE-1811
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1811
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Failsafe Plugin
> Affects Versions: 3.0.0-M5
> Reporter: Pavel_K
> Priority: Major
>
> I am testing version 3.0.0-M5 with two module-info in one project - one main
> and one for test. My test project is here
> https://github.com/PashaTurok/hibernate-h2-test4 . The problem is with
> resources. For example, I have src/main/resources/META-INF/persistence.xml
> file that is not copied to test module. Because of this it is not possible to
> find resource in test module and it is necessary to use something like this
> https://github.com/PashaTurok/hibernate-h2-test4/blob/292e2e683ad72487cbf8d2e5a35dde0d9255001a/src/test/java/com/foo/hibernate/h2/test4/TestIT.java#L72
> .
> In target/test-classes/META-INF/jpms.args I see:
> {code:java}
> --patch-module
> my.project=/home/..../hibernate-h2-test4/src/main/java,
> /home/.../hibernate-h2-test4/target/generated-sources/annotations
> {code}
> As I understand test module will NOT contain resources from the module under
> test? I mean that test module will NOT contain
> /home/..../hibernate-h2-test4/src/main/resources?
> That's why I suggest to include src/main/resources in test module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)