Cédric Champeau
Cédric Champeau
As mentioned in [libs.versions.toml](https://github.com/micronaut-projects/micronaut-gradle-plugin/blob/master/gradle/libs.versions.toml#L11) the `micronaut-platform` version that is used in this plugin is _purely for tests_. The plugin doesn't care which version you use in your application.
What version of Micronaut is this application using? Any chance you can share a reproducer? I suspect we need an AOT release built against Micronaut 4.2 but not fully convinced...
Alternatively, you can try to build the following branch of AOT: https://github.com/micronaut-projects/micronaut-aot/pull/260 (edit, this is now on `master`) Run `./gradlew pTML`, then in your project, add `mavenLocal()` as a repository...
The plugin actually makes use of bmuschko's Docker plugin so it seems complicated to support this out of the box. I'm not familiar with the `buildx` capability, but it's unlikely...
It seems unnatural to move configuration to `gradle.properties` to support tooling. Can you clarify what is the use case? With Gradle tooling support is achieved via the tooling API which...
Should this be in `micronaut-launch` instead?
I don't understand: the template adds those dependencies. That's what I just tried.
> Back then we moved a lot of logic to the plugins to hide it from users This makes sense to me: distinct plugin types model different kind of applications....
I'm sure we can fix the plugin if it does something wrong. But right now, do you agree that Micronaut Launch _is_ adding those dependencies, as shown in the screenshot?...
Another discussion point is whether this should also automatically add a dependency substitution rule (which would remove the need for having it in `micronaut-starter`). This would definitely require having a...