;> 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]
>
>
>
--
View this message in context:
http://www.nabble.com/Transitive-dep-misunderstanding-tf4560954s177.html#a13020618
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
Raffaele schrieb:
Hi all,
my very simple scenario:
project B dependes upon project A which dependes upon Junit, and so:
I guess you mean project A depends on project B which depends on Junit.
A --> B --> Junit
Project A also needs of Junit to compile its test classes, but I would like
t
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 depende
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 dep
ight 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
--
View this message in context:
http://www.nabble.com/Transitive-dep-misunderstanding-tf4560954s177.html#a13016209
Sent from the
