Could it perhaps be caused by putting the dependency in the parent as a
dependency rather than a version in the dependency management section?
You might want to reread the Maven documentation or one of the books
about using a parent POM to manage versions.
It works fine if you do it right.
Ron
On 24/04/2012 12:10 PM, Wayne Fay wrote:
In the Web Module (that inherits from the parent POM), the effective POM
shows a different older version. I thought this could be because of Spring
Projects and their dependency. Later, when I copied the POM entries from
Parent and pasted in the Web Module's POM, I got the right versions. I am
using Spring STS with Maven 3.0.3.
What is the version number of the parent and child from their pom.xml
files? If the versions are not snapshots, then Maven is most likely
doing things properly and you do not recognize some important aspects
of releases vs snapshots.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
