Reject SNAPSHOT versions in parser classpath dependencies#155
Reject SNAPSHOT versions in parser classpath dependencies#155
Conversation
Add a component selection rule that rejects SNAPSHOT versions when resolving parser classpath dependencies to ensure only stable releases are used.
shanman190
left a comment
shanman190
left a comment
There was a problem hiding this comment.
There are sometime valid uses for using snapshot dependencies. One example that comes to mind is how we try to get community authors to write recipes to help their users migrate to new versions. It's most desirable for that to happen on the inner development loop.
I feel like this is now begging the question of if type tables should be a generated resource as part of the build rather than a committed one. As a consequence, this sort of problem would disappear due to our -Preleasing=true flag.
|
Hmm; what prompted this was some flakiness in rewrite-testing-frameworks, because the I'm fine not to adopt this change, but I'd myself still lean towards using exact versions in type tables and check those in, since they wouldn't change unless entries are added/removed. That also makes our builds a little more reproducible, especially when new versions come out often. |
2 participants
Add a component selection rule that rejects SNAPSHOT versions when resolving parser classpath dependencies to ensure only stable releases are used.
The change extracts the detached configuration into a variable and applies a component selection rule that rejects any version containing "SNAPSHOT".