[
https://issues.apache.org/jira/browse/MNG-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816140#comment-17816140
]
Peter Palaga commented on MNG-7092:
-----------------------------------
bq. The "omit" is the one you want, if I understant correctly
Right.
bq. the "skip" would actually populate the local repository, think uses cases
like "go offline" (assuming plugin does not resolve anything dynamically).
Thanks for the explanation. It sounds like a useful scenario.
> Core mechanism for skipping mojos
> ---------------------------------
>
> Key: MNG-7092
> URL: https://issues.apache.org/jira/browse/MNG-7092
> Project: Maven
> Issue Type: New Feature
> Reporter: Peter Palaga
> Priority: Major
>
> The current practice is that mojo authors have to implement skipping on their
> side. It is easy to do, but it has a couple of disadvantages:
> * Not every mojo has a skip option
> * The naming conventions differ among mojos
> * Performance: the dependencies of the mojo need to be resolved, downloaded,
> classes loaded and initialized, config injected only to eval the skip option
> and do nothing. I have collected some numbers in
> https://peter.palaga.org/2020/10/29/skipping-maven-mojos-properly.html .
> I wonder if Maven core could provide a mechanism for skipping mojos without
> the above drawbacks?
> There could be some global naming convention, so that
> {{-Dorg.my-org.my-maven-plugin.my-mojo.skip}} or just `-Dmy.my-mojo.skip`
> would skip `my-mojo`.
> WDYT?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
