I think you can achieve this by defining the B artifact in your dependency
management section, with the scope set to provided. You can control your
transient dependencies through your dependency management section. I don't
think I've tried doing that for scope, but only for version. But I think it
should work; try it!
/Anders
On Fri, Nov 6, 2009 at 16:45, David Hoffer <
[hidden email]> wrote:
> I have what may be a unique case. In one of my child poms I want to depend
> on a pom type dependency (A) (i.e. i want to depend on a project that just
> specifies a bunch of dependencies). However for just one of the transitive
> dependencies (B) being brought into my project through this pom (A) I want
> to mark its scope as provided.
>
> I have tried adding a direct dependency on this artifact (B) using provided
> scope but I can't get it to take effect, it seems the other pom type
> dependency (A) takes presidence. I've also tried excluding (B) when I add
> the pom type dependency (A) and then add (B) directly but that doesn't work
> either.
>
> How can this be done?
>
