> Specifying versions in module level POMs opens the door to a module
> having the wrong version during the build which can show up as a method
> not found if the module was built with a version later than the one
> provided at runtime.
I never said that I expect the module level POMs to have the version.
They should inherit that from a (top) parent which should have the
version in a dependentManagement section.
I simply do not believe there is much to gain from having this in the
parent (which is what he seems to be doing):
<my.dep.version>1.2.3</my.dep.version>
<depMgmt>...<dep><g/></a><version>${my.dep.version}</version></dep>
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
