gharris1727 commented on PR #14064: URL: https://github.com/apache/kafka/pull/14064#issuecomment-1662806844
> As far as the epilogue output goes, I wonder if we're getting a little too detailed here... will users get much out of knowing the number of total locations/compatible locations? My justification for it was that a `pluginLocation` corresponds to an installed artifact for the typical users, and is a proxy for how many dependencies they have. I think this is useful context for the user of this tool to have, and it can also encourage healthy migration practices. For example, an SMT multi-tool package with tens of individual plugins may all be addressed at once with an upgrade. It will inflate the number of non-compatible plugins considerably, but only add 1 to the non-compatible locations. If someone uses `list` and sees that tens or hundreds of plugins are incompatible, they may skip the upgrading/contacting steps of the migration and just run `sync-manifests`. If they see that two or three locations are incompatible, they may be more inclined to upgrade first, knowing the number of dependencies they need to audit is small. -- 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: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
