> > Project dependencies are something that we are looking at for the > > future > of > > Maven. > > Could you elaborate?
Instead of stating a JAR as a dependency, you might state a project.xml as a dependency. This would enable transitive dependencies (you pick up all the deps of the subprojects you depend on automatically - eg depending on digester will give you beanutils even if you don't use and state it explicitly), and would also enable better location of project information related to dependencies. I think this is what you were referring to - that the project was referencing a JAR rather than a project? > 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 > > Sorry, should have specified you want "maven -X jar", as there is no default goal specified. You should also remove unitTestSourceDirectory from project.xml as there are none. I don't think this is hurting anything. > > 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. :( No, it's the latter. It's the accumulation of the dependencies used by your project and all the plugins in action, put into a reference for ant to use. > > Thanks for looking into this. No problems. Cheers, Brett
