[
https://issues.apache.org/jira/browse/MCOMPILER-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16398404#comment-16398404
]
Réda Housni Alaoui commented on MCOMPILER-328:
----------------------------------------------
[~rfscholte], in fact I can reproduce with the same project under Gradle:
[https://github.com/Cosium/jigsaw-elasticsearch-gradle]
So it looks like a pure ElasticSearch issue in fact.
You can close this one I think.
Thank you !
> Module not found when java services are involved
> ------------------------------------------------
>
> Key: MCOMPILER-328
> URL: https://issues.apache.org/jira/browse/MCOMPILER-328
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.7.0
> Reporter: Réda Housni Alaoui
> Priority: Critical
>
> I have a project using Maven and Java 9 that is unable to require
> elasticsearch automodule.
> I created a a project reproducing easily the issue with a README containing
> all the details:
> [https://github.com/Cosium/jigsaw-elasticsearch]
> Just clone it and run {{mvn clean package}}
> Build fails with:
> {{[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile
> (default-compile) on project jigsaw-elasticsearch: Compilation failure
> [ERROR]
> /srv/git/cosium/jigsaw-elasticsearch/src/main/java/module-info.java:[7,14]
> module not found: elasticsearch}}
> The same project compiles well with Gradle.
> Therefore I am inclined to believe the issue comes from Maven.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
