Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I was trying to add a dependency on StringTemplates. This is how my dependencies.yml file looked like:
require:
- play -> secure
- play -> crud
- org.antlr -> stringtemplate
And I got errors. When I added a specific version of stringtemplate:
- org.antlr -> stringtemplate 4.0.2
everything worked.
So, just to make sure I understand – I have to specify a version or range of versions for a 3rd party dependency, correct?
The third party dependency management uses the Maven/Ivy scheme (because it is based on Ivy), which translates to a file name of
{name}-{version}.jar.While I think it is possible to simply use the latest version (either with SNAPSHOT as version or some wildcard, but I’m no expert here), it seems to be best practice to make versioning explicit.