On 6/15/07, Johan Iskandar [EMAIL PROTECTED] wrote:
Is there anyway for us to declare in the parent project's pom a
restriction on the set of jar's version to use in building the whole
project?
Set the versions in dependencyManagement (and pluginManagement) in
the parent, and then don't use
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Set the versions in dependencyManagement (and pluginManagement) in
the parent, and then don't use version elsewhere.
This doesn't 'force' it -- a child project can still override the
choice if it wants to.
Does this
This doesn't 'force' it -- a child project can still override the
choice if it wants to.
Does this means that if I had 3rd party modules I would also need to
remove all version of the 3rd party modules?
Sorry what I meant was.. 3rd party modules's poms?
On 6/15/07, Johan Iskandar [EMAIL PROTECTED] wrote:
Does this means that if I had 3rd party modules I would also need to
remove all version of the 3rd party modules?
Sorry what I meant was.. 3rd party modules's poms?
No... your definitions in dependencyManagement should be closer and
take
Considering this set..
com.a:a
project
...
groupIdcom.a/groupId
artifactIda/artifactId
packagingjar/packaging
version1.0/version
namea's project/name
dependencyManagement
dependencies
dependency
