Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The dependency plugin uses the same resolution mechanism as everything else. It may be that your repositories are not updating the metadata because the is set to <em>never</em> or <em>weekly</em> or something. You can force Maven to refresh all the remote repository metadata by running with a -U.</p> <p>The dependency plugin also doesn't overwrite downloaded dependencies by default if they already exist in the target. You can do a clean or configure the goal to force overwrites. There are three parameters you can set to true: <em>overWriteIfNewer</em>, <em>overWriteReleases</em>, and <em>overWriteSnapshots</em>. See <a href="http://maven.apache.org/plugins/maven-dependency-plugin/copy-mojo.html" rel="nofollow noreferrer">the documentation</a> for more details.</p> <p>Edit: based on your updated question, the problem is that you are using a dependency range. Ranges are fine as long as there is something to resolve the version (for example you have the version defined in the parent project or in your dependencies section). If you change the range to an exact version, or use one of the <a href="http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-pom-syntax.html#pom-relationships-sect-latest-release" rel="nofollow noreferrer">LATEST or RELEASE keywords</a>, Maven will be able to resolve the version number (though be aware that those keywords carry their own risks.</p> <p>I'd recommend defining a dependencyManagement section in your parent with the versions you use, then your projects can inherit those versions. I answered another question about this recently, I'll post a link if I find it</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload