Hi,
Everything in META-INF/service has to move, unless it is following the
SPI structure.
But just us moving will not allow Groovy libraries to define extension
methods sadly.
Am 22.02.2018 um 10:56 schrieb Paul King:
After moving the Extensions file, it looks like the only other file in
Cédric's list that causes Java 9's ModuleFinder a problem is Groovy's
extension module file:
META-INF/services/org.codehaus.groovy.runtime.ExtensionModule
I'll also see what is involved in moving that (with a fallback to the
current location).
Cheers, Paul.
On Thu, Feb 15, 2018 at 3:49 AM, Jochen Theodorou <blackd...@gmx.org
<mailto:blackd...@gmx.org>> wrote:
Am 14.02.2018 um 03:34 schrieb Paul King:
Any objections if I look into moving the Extensions file from
META-INF/services to META-INF/groovy (with a fallback to the
current one). But not for 2.4.x.
in the meantime I know that META-INF/services has been reserved for
the normal purposes and everything else is indeed not valid. You can
find this in some javadoc comment on some class... somewhere. I can
look for it again if you want to (of course that is java9+ only)
I still think a groovy library as module will not be able to expose
its extension methods this way, which means we will most probably
not even be able to keep the file and will have to move to a SPI
structure... but moving to META-INF/groovy is probably a good first step
bye Jochen
