Guillermo Mazzola

> Please use the following solution: > https://gist.github.com/ahulyk/149aa35b228f0711bc530cb6dcc0e6ce Accessing the `Application` context is a bit hacky and won't work for libraries modules. Is there any way to provide instances of...

Hi @rhysd, I see there is activity in this repo. Any chance to get this one reviewed? We are currently using a forked internal version of your tool. Great work...

Hi @rhysd, I've rebased the code, simplified the solution and now all tests seem to be OK. It would be nice to hear back from you, this has been ignored...

Just faced this issue today, and @stefreak's workaround is not working to me 🤔

> > Just faced this issue today, and @stefreak's workaround is not working to me 🤔 > > @gmazzo Can you share what went wrong? Then I could edit my...

As for my current understanding, the whole concept of dealing with tasks is an antipattern on Gradle. Projects Tasks are meant to be artifact's providers and external projects should not...

Elaborating on this, what I meant at #598: > Variants are there, it's seems to a matter of the internal plugin resolution strategy. By this, what I meant is that...

Researching a bit deeper, it seems this is actually caused by JGIT implementation, I am right? I thought JGIT was a pure java implementation, why is running the host `git`...

I'd say this issue is caused by JGit and every plugin that relies on it will face the same. It seems it's accessing `.gitconfig` on ins initialization by a couple...

Yeah no hurries. I was talking a look and it seems there is no way no hook on `jgit` to delegate the process creation to Gradle's `exec`. So one option...