You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Dees, Ian (GE Healthcare)" <Ia...@ge.com> on 2007/03/16 19:14:20 UTC

How Does Maven Handle This?

If I have a dependency tree similar to this:

projectA depends on projectB-1-01-SNAPSHOT
projectA depends on projectC-1-00
projectC depends on projectB-1-00

How does maven handle running tests on projectA, for example?

In our case, projectB-1-01-SNAPSHOT should be API-compatible with
projectB-1-00 (i.e. we only added new method signatures and classes, no
changes), but when compiling projectA, we get compile errors because
javac does not ever see the changes introduced in the
projectB-1-01-SNAPSHOT.

I'm assuming that maven will put both versions on the classpath when
executing the compile, and that javac will pick the first JAR (which
could be either one). I would expect, though, that if the older JAR is
first, javac would continue on to the newer JAR and pick up the added
classes.

I'm not crazy, right?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org