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.
HTH,
Jane
Ken Cavanaugh wrote:
> Lloyd Chambers wrote:
>> Should gmbal be included without a version? Does the root level
>> override?
> I think no version = most current version, which would be 3.0.0-b004
> (today).
> It would probably be best to depend on 3.0.0, in case I move to a
> 3.1.0 or 3.0.1
> version at some point. A dependency on 3.0.0 should always mean the
> latest version
> of 3.0.0, currently 3.0.0-b004.
>
> Ken.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>