You can apply spotless-changelog multiple times in a multi-project build (example), but each instance needs to have a distinct changelog file, as well as a distinct tagPrefix, otherwise you will get errors related to duplicate tags, such as #24.
It would be nice to proactively check for this condition within the plugin and warn the user. Task configuration avoidance and configure-on-demand mean that it won't always be perfect, but there are certainly some cases where we could help the user understand that it has been configured incorrectly.
You can apply spotless-changelog multiple times in a multi-project build (example), but each instance needs to have a distinct changelog file, as well as a distinct
tagPrefix, otherwise you will get errors related to duplicate tags, such as #24.It would be nice to proactively check for this condition within the plugin and warn the user. Task configuration avoidance and configure-on-demand mean that it won't always be perfect, but there are certainly some cases where we could help the user understand that it has been configured incorrectly.