Jane is correct. I suggest a look at the maven documentation on this
topic [1].
Thanks,
Sahoo
[1]
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management
Jane Young wrote:
> All the child POMs should not have the version defined. The version
> information should be inherited from the parent POM.
>
> Ken Cavanaugh wrote:
>> Jane Young wrote:
>>> No, the most current version will not be used.
>>> Since org.glassfish.gmbal:gmbal:3.0.0-b004 artfiact is defined in
>>> dependencyManagemet of the parent level pom.xml, the version
>>> information is inherited to the child poms. No need to include the
>>> version. Defining the dependencies in the parent level helps
>>> centralize the dependency information in one pom. We don't want
>>> multiple child poms depending on the same artifact with different
>>> versions. Just think, it would be really complex for the packager
>>> module to figure out which version to include in v3.
>>>
>> OK, so what you want is the top-most POM should have a fully
>> specified version (currently 3.0.0-b004),
>> and all dependent POMs should just specifiy 3.0.0?
>>
>> Thanks,
>>
>> Ken.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>