> Project dependencies are something that we are looking at for the future of > Maven.
Could you elaborate? > I can't see why this isn't working, but the classpath is definitely not > right. Can you send me the full output of maven -X to [EMAIL PROTECTED] The --verbose output was linked at bottom of the first e-mail, but here it is again: http://gump.dotnot.org/jakarta-gump-test/work/build_jakarta-gump-test_gump-test-maven2.html Oh, you want some -X thingie ... ok, here it is (it isn't large, so I'll share...) [EMAIL PROTECTED] maven-project2]$ maven -X __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT [DEBUG] Adding reference: maven.dependency.classpath -> /var/gump/jakarta-gump-test/maven-project1/target/gump-test-maven1-0.1.jar [available] [VERBOSE] Found: src/java [available] [VERBOSE] Unable to find src/test to set property unitTestSourcesPresent [DEBUG] Adding reference: maven-classpath -> [DEBUG] Adding reference: maven.compile.src.set -> BUILD SUCCESSFUL Total time: 5 seconds Finished at: Wed Feb 11 18:00:08 CST 2004 Q: Is the 'maven.dependency.classpath' something for Maven to use for itself, or something for Maven to use for projects it is working on? Looks scarily liky the former. :( Thanks for looking into this. regards, Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
