may it be that the junit only has the scope='test' in
the pom and this scope will not be taken by the
eclipse:eclipse?
For what i know eclipse does not have an own 'test'
classpath but only one-for-all.
LieGrü,
strub
--- Nick Stolwijk <[EMAIL PROTECTED]> schrieb:
> A.F.A.I.K. transitive dependencies only count at
> runtime. You need those
> dependencies to run your program. If you need a
> dependency at compile
> time, it is your own dependency and not some
> transitive dependency.
>
> Hth,
>
> Nick Stolwijk
>
> Raffaele wrote:
> > Hi all,
> > my very simple scenario:
> > project B dependes upon project A which dependes
> upon Junit, and so:
> > A --> B --> Junit
> >
> > Project A also needs of Junit to compile its test
> classes, but I would like
> > that project A didn't define directly the
> dependency from Junit.
> >
> > Can Junit in this scenario be considered a
> transitive dependency for project
> > A? I believe yes.
> >
> > When I load my projects in Eclipse 3.3 after
> obviously mvn eclipse:eclipse,
> > I see compile error on project A which it don't
> find the reference to
> > Junit....
> > But how can it be possible? Shouldn't the
> references of right jars be
> > arranged?
> >
> > The compile error is also visible when I try from
> command-line to run mvn
> > test on project A folder.
> >
> > Thank you very much,
> > best regards.
> > Raffaele
> >
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
Wissenswertes für Bastler und Hobby Handwerker. BE A BETTER HEIMWERKER!
www.yahoo.de/clever
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
