Re: Incomplete classpath due to scope resolution for test/provided

2008-08-04 Thread Mark Hobson
2008/7/28 Mark Hobson <[EMAIL PROTECTED]>: > You're right that provided is not transitive, although this example > relates to scope resolution which occurs when an artifacts has two > different scopes. See: > > http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#Dep

Re: Incomplete classpath due to scope resolution for test/provided

2008-07-28 Thread Mark Hobson
2008/7/28 Stephen Connolly <[EMAIL PROTECTED]>: > AFAIK, provided is not transitive, so a provided dependency is assumed to be > provided by any consumer of b You're right that provided is not transitive, although this example relates to scope resolution which occurs when an artifacts has two diff

Re: Incomplete classpath due to scope resolution for test/provided

2008-07-28 Thread Stephen Connolly
AFAIK, provided is not transitive, so a provided dependency is assumed to be provided by any consumer of b On Mon, Jul 28, 2008 at 10:48 AM, Mark Hobson <[EMAIL PROTECTED]> wrote: > Ping.. can anyone share some insight on this please? > > Mark > > 2008/7/22 Mark Hobson <[EMAIL PROTECTED]>: > > Hi

Re: Incomplete classpath due to scope resolution for test/provided

2008-07-28 Thread Mark Hobson
Ping.. can anyone share some insight on this please? Mark 2008/7/22 Mark Hobson <[EMAIL PROTECTED]>: > Hi there, > > I've encountered an issue with the scope resolution for nearest test > and farthest provided scenario. Consider the following projects: > >a -> commons-lang >b -> commons-

Incomplete classpath due to scope resolution for test/provided

2008-07-22 Thread Mark Hobson
Hi there, I've encountered an issue with the scope resolution for nearest test and farthest provided scenario. Consider the following projects: a -> commons-lang b -> commons-lang c -> a:test, b:provided Where -> denotes a dependency and group ids, types and versions have been omitt