Unable to derive module descriptor for gradle-api-5.6.2.jar — Provider class moduleName=model-core not in module

[Plugins]

Hi,

{And sorry about my messages not being connected to the thread. I can't
get my webmail to do the right thing}

Github.com have finally unflagged my account now. Their „spam
blocker“ objected to something of mine somewhere — allegedly.

Anyway, the two issues and the one pull request [1] are visible again.


----
[1] http://bit.ly/PR11039
----

-------- Original Message --------
Subject: RE: Re: Unable to derive module descriptor for gradle-api-5
.6.2.jar — Provider class module Name=model-core not in module
From: "Plugins" <plugins at lingocoder.com>
Date: Tue, October 15, 2019 10:54 am
To: "Alex Buckley" <alex.buckley at oracle.com>,
jigsaw-dev at openjdk.java.net

Yeah. Sorry about that. I don't know what's going on. But only seconds
after I pushed my change up to my forked gradle/gradle repo yesterday,
for some reason github.com flashed an angry red „Your account has been
flagged. Please contact support...“ message on every page I visit on
github. I contacted github.com support several hours ago. But they still
haven't replied.

They've disappeared from Gradle's issue page. They're titled
„Compliance with Groovy 2.5's Standard Mechanism...“ and 
„Compliance with the JDK's Standard Mechanism...“. I can only see
them — with the „...flagged...“ message emblazoned across the top
— when I'm logged into github.com. 

I was afraid something like this would happen. So shortly after I first
submitted the Groovy one, I saved it on the Wayback Machine [1] Stuff
like this isn't good for that conspiracy theorist in me ;) 


----

[1] http://bit.ly/11028bak

----


-------- Original Message --------
Subject: Re:__Unable_to_derive_module_descriptor_for _gradle-api-5
.6.2.jar_—_Provider_class_module Name=model-core_n_ot_in_module
From: Alex Buckley <alex.buckley at oracle.com>
Date: Tue, October 15, 2019 8:50 am
To: jigsaw-dev at openjdk.java.net

On 10/14/2019 9:07 PM, Plugins wrote:
> I've reported to Gradle's issue tracking system, both the 
> java.security.Provider configuration file issue [1] and the 
> org.codehaus.groovy.runtime.ExtensionModule configuration file issue [2].

Thanks very much. Strangely, AFAICT, the two issues you submitted have 
disappeared -- they return 404 errors, and do not appear in the issue
list:

http://bit.ly/Issue11027
-> https://github.com/gradle/gradle/issues/11027

http://bit.ly/Issue11028
-> https://github.com/gradle/gradle/issues/11028

Alex