gnodet commented on PR #1086: URL: https://github.com/apache/maven/pull/1086#issuecomment-1509116733
> To demonstrate: https://github.com/cstamas/plugin-clash/blob/main/README.md (and project that creates two different GA plugins and use them in build). Hence, IMHO any coherence with console output would be misleading: prefix _cannot uniquely identify a plugin_ I'm not sure how that's relevant. Your syntax supports wildcards, which definitely cannot uniquely identify a plugin. My points is not to restrict the supported syntax to `pluginPrefix[:version]:goal` and `groupId:artifactId[:version]:goal`, but to support it. And I would also support the optional `e` after, i.e. `pluginPrefix[:version]:goal[:executionId]` and `groupId:artifactId[:version]:goal[:executionId]`, but more importantly, at least support `pluginPrefix:version:goal` so that people can simply copy/paste from the console to skip a given plugin goal, instead of having to find out the `groupId:artifactId`. For example, how can you simply relate `spotless:2.28.0:apply (default)` from the console output to `com.diffplug.spotless:spotless-maven-plugin:apply` when that plugin is defined in a parent outside of the project ? I'd like to find a syntax that would support just copy/pasting the output from the console, certainly not be limited to that. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
