Under some circumstances, Maven fails to resolve dependencies with version "${project.version}" - instead of using the project version, it tries to lookup version "2.4.1".

As stated here and here, the reason for this is a "version" system property that is set by JDK 1.4.2 and kind of overwrites "project.version".

I stumbled across this problem in two situations:

  • When using the Maven dependency mechanism in an Ant script. The problem has to do with the "xslt" (or "style") Ant task, so the quick resolution is:
    Call all "dependencies" tasks before any "xslt" or "style" tag :-/
  • When using the Maven Eclipse plugin. Workaround: Use Java 5 as Eclipse runtime environment.