Version 5.0 points to upstream SNAPSHOT dependency #32
Replies: 2 comments
-
Greetings. Why would that be a problem please? |
Beta Was this translation helpful? Give feedback.
-
Why snapshots are a problem? The whole ecosystem of maven dependencies depend on fixed, released versions that have been verified. People want to know what they are consuming. With SNAPSHOTs this is not case. Every time I build my project and it pulls your project it will get whatever latest is that snapshot which introduces uncertainty. For example, my company does not allow services to be build if their dependencies contain snapshots. And I am not even touching the issue of supply chain security which is very real and pressing... I can probably get around this issue using dependency management to pin the version to the latest release version but I think you should produce release without snapshots |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
JSQLFormatter 5.0 has
JSQLParser 5.1-SNAPSHOT
as a dependency as shown here [1] which is a problem for a number of reasons.[1] https://repo1.maven.org/maven2/com/manticore-projects/jsqlformatter/jsqlformatter/5.0/jsqlformatter-5.0.pom
Beta Was this translation helpful? Give feedback.
All reactions