I have a parent pom that has two modules, A & B. B depends on A.
A depends on P which is a 3rd party jar with provided scope. The task of module A is to combine the contents of A & P, this sum is the output of A. Now when we build this (clean install) at the parent pom on two systems we get two different behaviors. System 1: (XP w/ maven 2.1) Everything works as expected. The build of B depends on the final output jar of A in its target folder. I.e. with -X turned on I see its depending on .../target/A.jar System 2: (Vista, w/ cygwin, maven 2.?) Build fails. The build of B does not depend on the final output jar of A, rather it depends on A's target/classes folder. I.e. with -X turned on I see its depending on .../target/classes (Note the build fails here because the classes folder is not enough, it would also need the P dependency which is not available because it's scope is provided. The desired behavior is as system 1, where dependent builds depend on the final output of A.) Whey are these builds different? System 1 is the assumed correct behavior, right? Is this somehow configurable?? -Dave
