Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
12.2
-
None
Description
Micronaut 3.0 is going to deprecate maven exec:exec, which is now used by the IDE to issue these actions
- Run, Run-single
- Debug, Debug-single
- Profile
The new supported way to invoke maven Micronaut projects will be mn:run using Micronaut's io.micronaut.build:micronaut-maven-plugin.
Maven support however has pluggable support just for different packaging type. Here, we would want to inject or redefine actions based on POM's or effective POM's contents.
The idea is to allow to plug "something like" org.netbeans.modules.maven.spi.actions.MavenActionsProvider for a specific inherited group:artifactId{:version}, or in a generic way so that a provider can inspect the model and decide dynamically. Packaging could be also specified, as that defines the 'base' processing in most cases.
Both approaches has to be prepared for the case that the inherited POMs can be resolved later in the project's life, e.g. during the priming build.
This way, we can inject / override the actions with mn:run goal for specifically Micronaut projects, and keep the maven's core generic/clean.