groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü (JIRA) <j...@apache.org>
Subject [jira] [Created] (GROOVY-8471) Contents of META-INF/services/org.codehaus.groovy.source.Extensions conflict with Maven/Jisaw
Date Tue, 06 Feb 2018 15:21:00 GMT
Ceki Gülcü created GROOVY-8471:
----------------------------------

             Summary: Contents of META-INF/services/org.codehaus.groovy.source.Extensions
conflict with Maven/Jisaw
                 Key: GROOVY-8471
                 URL: https://issues.apache.org/jira/browse/GROOVY-8471
             Project: Groovy
          Issue Type: Bug
    Affects Versions: 2.4.13, 3.0.0-alpha-1
            Reporter: Ceki Gülcü


>From what [I can gather|http://markmail.org/thread/nekeppbvwrfl7hbb#query:+page:1+mid:qtqqcfrw6us6aupz+state:results],
Jigsaw module resolution analyzes the contents of module-info.class, MANIFEST.MF and META-INF/services/*
files. 

As such, it turns out that the contents of {{src/resources/META-INF/services/org.codehaus.groovy.source.Extensions}}
prevents groovy-*.jar from being loaded as an automatic module, at least within a Maven build.

[~rfscholte] has pointed out that this is not a Maven specific problem as can be verified
in JShell by invoking: 
{code}
java.lang.module.ModuleFinder.of(java.nio.file.Paths.get(artifact)).findAll().stream().findFirst().get().descriptor().name()
{code}





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message