Wayne Fay wrote:
>> 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>
http://repo1.maven.org/maven2/com/thoughtworks/xstream/xstream-
parent/1.4.2/xstream-parent-1.4.2.pom
IMHO, it is much easier to get an overviewand it is a lot less error-prone
if some artifacts share the same version (e.g. ejb and ejb-client). And if I
look at our companies master POM with ~500 version entries ... ;-)
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
