I have just remeber my problems with this: in many cases you define the
versions with DepencyManagement in a parent POM to align them in all the
modules, but, for one child (or via import scope) module you want them to be
provided beacause other module provides them. Then, in your child pom you
do
Yes, it has sense.
Thank you.
Anders Hammar wrote:
>
> Well, as I see things, if you specify the artifact as provided then you
> also want to define the version that is provided. IMO you do want to use
> the same version in your Maven build as you're going to use in the
> targeted environment.
Well, as I see things, if you specify the artifact as provided then you also
want to define the version that is provided. IMO you do want to use the same
version in your Maven build as you're going to use in the targeted
environment. In fact, this was one of my key points in a Maven talk I did at
I see. Thank you.
So we can modify version, version an scope, but not, only scope. This is a
problem when you only want using it to "upgrade" a dependency to "provided".
Then you are also manipulatig the version that should be resolved by Maven.
So it seems its not a good idea using it to exclud
I'm not sure about the optional tag, but it does apply to version.
DependencyManagement is where you can specify the version to use for
transitive dependencies.
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management
/Anders
softwarepills wro
To clarify more the matter.
Should we think about DependencyManagement no only as a default value
provider, but also as a modifier of inherited dependencies?
Does it apply to other parameters like the itself and ?.
Jörg Schaible-3 wrote:
>
> softwarepills wrote:
>> I usually think in Depende
Short and clear.
I didn't found this in either the two books of Maven or in the Maven docs.
Thanks a lot.
softwarepills wrote:
>
> I usually think in DependencyManagement as a "by default" section, i mean,
> the version and scope you set in DependencyManagement is the version and
> scope you
softwarepills wrote:
> I usually think in DependencyManagement as a "by default" section, i
> mean, the version and scope you set in DependencyManagement is the
> version and scope you get if ommited in the real dependency in the POM
> and child POMs.
>
> But, i have found that if i insert provid
