[jira] [Resolved] (GROOVY-8471) Contents of META-INF/services/org.codehaus.groovy.source.Extensions conflict with Maven/Jisaw

["Paul King (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GROOVY-8471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul King resolved GROOVY-8471.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 2.5.0-beta-3

Merged into master, 2_6_X and 2_5_X for now. If there is sufficient demand it seems low risk to also do 2_4_X but 2_5_X will be in somewhat better shape wrt jdk 9, so perhaps better to leave 2.5.0 as the recommended (once released) JDK 9 version.

> 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: 3.0.0-alpha-1, 2.4.13
>            Reporter: Ceki Gülcü
>            Assignee: Paul King
>            Priority: Major
>             Fix For: 2.5.0-beta-3
>
>
> 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)