I may be wrong, but setting
<project>
<version>${project.version}</version>
for me is a nonsense.
You're refering the element you're declaring, it's a kind of cyclic link.
The only usage I made for ${project.version} in multi-module project is to
use it in dependencies, to get dependencies that have just been built
previously in the reactor, and so latest snapshot versions (kind of
continuous integration on all modules).
At least, you should have one fixed version in your pom to determine the
artifact coordinates, in project.version or in project.parent.version (if
you omit project.version, project.parent.version is being used).
To modify the version in all your modules, you can:
- use maven release plugin
- declare a property in project.version (not ${project.version}...) and pass
it through command line. In maven repo, the pom of the artifact should have
the value of the property and not the property itself.
--
View this message in context:
http://maven.40175.n5.nabble.com/How-to-stop-maven-to-check-the-dependency-s-pom-xml-tp4332100p4333938.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
