Should support core extensions

[marcphilipp]

Core extensions don't seem to get applied when using mvnd. Is that a known issue/limitation?

To reproduce simply clone https://github.com/gradle/maven-build-scan-quickstart, and run mvnd validate vs. ./mvnw validate. The latter prints a build scan link at the end, while the former does not.

[ppalaga]

This is an issue known solely thanks to your report :) Thanks!

[famod]

Big 👍 from me as this would also enable the combination of mvnd and https://github.com/vackosar/gitflow-incremental-builder

[famod]

It seems extensions registered in pom.xml via <extensions> or as plugins with <extensions>true</extensions> are not affected!

[ppalaga]

We should test with .mvnd/extensions.xml

[gnodet]

Fwiw, extensions have been removed from DaemonMavenCli in the initial work to allow the container to be created and reused.

I'm going to check if we can bring that back somehow.

[gnodet]

@marcphilipp fwiw, the Gradle extensions uses a non standard input handler, so even with #181 and a fix #180, this would not solve the usage of the Gradle extension. It would require a custom fix to provide an implementation of com.gradle.maven.extension.internal.dep.org.codehaus.plexus.components.interactivity that could delegate to the one that a fix for #180 would provide.

[marcphilipp]

@gnodet Thanks for looking into it! I'll take a closer look once #180 is resolved.