Robert Elliot

See the `no-deps-jpms-plugin` branch of this repo: https://github.com/Mahoney-playground/gradle-jpms-app/tree/no-deps-jpms-plugin Fails as so: ``` $ gw --no-build-cache assemble > Task :app:compileKotlin FAILED e: Module uk.org.lidalia.jpmsapp.utilities cannot be found in the module graph...

Thanks - just tried your sample and it definitely works, so I guess I need to try and work out what I'm doing differently.

I am completely baffled. I've basically copied your example verbatim in this branch, just with slightly different modules: https://github.com/Mahoney-playground/gradle-jpms-app/tree/no-deps-jpms-plugin and it fails: https://github.com/Mahoney-playground/gradle-jpms-app/runs/5706169489?check_suite_focus=true I've spent half the day trying to...

Not sure... `main` on that repo, which is JPMS but with conventional dependency declaration, works fine. The thing that `main` on that project, and your sample, have in common is...

Yes, sorry, that was a rubbish bug report - rushing to get to bed. Added the obvious extra details.

I realise I've muddied the waters by using a snapshot version of gradle, but I see exactly the same behaviour reverting to gradle 6.6.1.

Updated the bug report to a branch using gradle 6.6.1 - same behaviour.

I'll try and get it into a more manageable form, but I've spiked it and this works: * Create a program to run at startup on the host that evaluates...

On linux I think all the networks using the bridge driver are addressable from the host, so I'd been planning on parsing the output of `docker network ls` and `docker...

Last thing I thought of was to bundle this all up in a brew recipe that would depend on docker for mac & tuntap, so setting up docker for mac...