Ok, I tried to reproduce my problem on a simple test example and I think there is some problem with my project. It seems that the plugin behavior is correct : provided dependencies are not transitive. So as projectB and projectC are provided, if projectA depends on projectB that depends on projectC, projectA does not depends on projectC.
Thanx for your patience Seb 2006/4/27, Giorgio Gallo <[EMAIL PROTECTED]>: > > I specified "provided" as scope - it still generates a dependency in > eclipse... > > Since you miss the <version> in your dependencies, i guess you're using > <dependencyManagement> in the parent poms - I tried that too and it works... > > What do you get in your .classpath file in projectA? You should have something > along the lines of: > <classpathentry kind="src" path="/projectB"/> > > On Thursday 27 April 2006 16:10, Sebastien Cesbron wrote: > > Do you have your dependencies declared as "provided" ? > > > > I mean in project A I have > > <dependencies> > > <dependency> > > <groupId>project</groupId> > > <artifactId>projectB</artifactId> > > <scope>provided</scope> > > </dependency> > > </dependencies> > > > > and in project B > > <dependencies> > > <dependency> > > <groupId>project</groupId> > > <artifactId>projectC</artifactId> > > <scope>provided</scope> > > </dependency> > > </dependencies> > > > > If I use the goal eclipse:eclipse on project A parents it works only > > if my libraries are not in provided scope > > > > [...] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
