Good suggestion, I will do that. Thanks for your help. On 12/14/06, Guillaume Duchesneau <[EMAIL PROTECTED]> wrote: > > Hum... You are right... I think my problem is due to the fact that the > provided scope is not transitive. My case is that projectA depends on > projectB which depends on servlet-api (provided scope). Tests on > projectB needing servlet-api pass but not those in projectA that > indirectly uses servlet-api via some projectB classes. > > I think I will have to redeclare that dependency in projectA too :-( > unless there is a way to declare multiple scope for a dependency...
I think that's the right answer. Even if provided scope were transitive, I don't think test scope is, so you'll need to do this anyway :-). One thing to consider is if you can use a <dependencyManagement> section in a common parent POM to define the version numbers of shared dependencies like this. That way, you could upgrade from, say, servlet 2.4 to servlet 2.5 more easily by changing the version number just once. Thanks > > Guillaume Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
