Feature Request: Maven Lifecycle Mapping view could run plugin executions by double click

[caldy2000]

Request submitted based on Eclipse 2024-09 M2

i'm using m2e, i found the Maven Lifecycle Mapping view could list plugin executions in the pom.xml, but there is no UI operations that could trigger execution be invoked neither double click nor right click.

So, i'm wondering, to make these executions listing there could be invoked by click, it can save time we used to operate with command line. Does this operation is practicable?

Usually, plugin executions has a phase to bind by default, or declare a phase to bind manually, when we're coding, if going to execute a plugin execution directly, we can do it in a command line interface.

Thanks.

[laeubi]

i'm using m2e, i found the Maven Lifecycle Mapping view could list plugin executions in the pom.xml, but there is no UI operations that could trigger execution be invoked neither double click nor right click.

This view is mainly for debugging / informal purpose and list what is executed (or not) automatically during incremental build, what would be your expected behavior on double an/or right click?

So, i'm wondering, to make these executions listing there could be invoked by click, it can save time we used to operate with command line. Does this operation is practicable?

You can righ click on the project and Choose Run As (with some predefined shortcuts) or use "Maven Build" to trigger any command from the UI.

Usually, plugin executions has a phase to bind by default, or declare a phase to bind manually, when we're coding, if going to execute a plugin execution directly, we can do it in a command line interface.

See above it is a bit unclear what exactly is the desired behavior.

[caldy2000]

This view is mainly for debugging / informal purpose and list what is executed (or not) automatically during incremental build, what would be your expected behavior on double an/or right click?

For instance,

the compiler plugin has added an execution which id is "lintAll-compile", and the view list it also,

Expect: i can double click this item in the view, m2e could run this execution directly, the same effect as mvn compiler:compile@lintAll-compile work in project root directory.

You can righ click on the project and Choose Run As (with some predefined shortcuts) or use "Maven Build" to trigger any command from the UI.

Expect no need to add Maven Build configurations for specific plugin executions(goals) use, just select it from the view, double click on it, and it works

[laeubi]

Expect: i can double click this item in the view, m2e could run this execution directly, the same effect as mvn compiler:compile@lintAll-compile work in project root directory.

How is this different from what you already see? e.g. exactly this happens automatically on each change in the project without the need to do anything manually.