Introduce modules-ignore to replace projects and scala-versions input #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After discussion, it appears that exclusion of single modules is more useful than exclusion of entire projects, on all Scala versions, or entire scala versions, on all projects. The main argument is that we should publish all graphs, on all projects and all scala versions, except if there is a non-easy-to-solve problem on a module. In which case it is better to exclude this particular module rather than non publish the graph.
In this PR:
sbt-dependency-submissionbase-dirtoworking-directoryprojects,scala-versionsinputmodules-ignoreinput (plain text, no glob)sbt-plugin-versioninput. It is not needed, the action should always use the current version of the plugin.on-resolve-failureinput. Default iserror, one can switch towarnto ignore the dependency resolution failures with warnings.Tested in:
on-resolve-failure: false): https://github.com/adpi2/sbt/runs/7340204567