getRuntimeArtifacts and provided scope

[Mathieu <ma...@iscpif.fr>]

Hi,

we are trying to implement a maven Mojo. In the Mojo we call the
getRuntimeArtifacts method
on the maven project object in order to list all the dependencies which
need to be present
at runtime. The problem is that we don't get any "provided scope"
dependency  whereas one is defined
in the pom.xml on the builded project (in the result of
getRuntimeArtifacts the provided dependency
does not show up).

Any idea on that?

Mathieu

Re: getRuntimeArtifacts and provided scope

[Jörg Schaible <jo...@gmx.de>]

Hi Mathieu,

Mathieu wrote:

> Hi,
> 
> we are trying to implement a maven Mojo. In the Mojo we call the
> getRuntimeArtifacts method
> on the maven project object in order to list all the dependencies which
> need to be present
> at runtime. The problem is that we don't get any "provided scope"
> dependency  whereas one is defined
> in the pom.xml on the builded project (in the result of
> getRuntimeArtifacts the provided dependency
> does not show up).
> 
> Any idea on that?

This is exactly, what provided means: It's provided by the runtime platform, 
your application can expect those artifacts (resp. the classes of those 
artifacts) to be present without having to deliver them. E.g. it does make 
sense to set javax.activation:activation to "provided", because it is 
nowaday part of the Java runtime.

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org