Yo Nix my friend, Your expectations are not in line with how maven documentation states maven works. Check out http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.htmlthere you'll find a table which shows how each of the scopes affects transitive dependencies. In your case, in compile phase of your project, project's compile scoped dependency will be present, but transitive, provided scoped, dependency will be omitted. Why it works on your colleague's environment, there's certainly a rational explanation but without more details, it will remain a mystery.
Regards, Stevo. On Sun, Sep 21, 2008 at 11:44 PM, Nikola Milutinovic <[EMAIL PROTECTED]>wrote: > Hi all. > > I have run into a strange problem with transitive dependencies. This shows > itself both under m2clipse and Maven 2.0.9. However, it does not manifest > itself on other installation of the same m2clipse (latest stable) with my > colleague. > > A project has a dependency on org.springframework:spring-webmvc:2.5.5, > which has a dependency on javax.servlet:servlet-api:2.4 (scope=provided). > > I would expect that this transitive dependency gets brought in in both > m2clipse Maven Dependencies and Maven2 reactor for compile phase. This, > however, does not happen on two installations of m2clipse that I have. It > also fails in command line. I have attached a screenshot of dependency > graph, the POM and CLI output. > > Also, when I add the dependency myself to the project, with scope=provided, > everything works. > > Any comment? > > Nix. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > >
