We've gotten a bit further with this, however, we are still finding that we are having some problems when using aggregator poms.
The original situation has been fixed after discovering a problem with how the source directory was in one of the parent pom files. Now we've found that if we have a master aggregator pom that has ProjectA, ProjectB, and ProjectC in it, where the tests in ProjectB depend on the tests in ProjectA, the test directory from ProjectA doesn't get added to the classpath, but rather, the source directory gets added twice. We also noticed that when using the aggregator, the classpath elements refer to the source code directories, and not to the local repository for any dependencies that were also being built as part of the aggregator. If there was a way to change this so that the aggregator always looked at the local repository, regardless of what else is being built at the same time, this would fix our problem - if we build ProjectA separately and do not include it in the aggregator, the aggregator builds fine, as it refers to the jars in the local repository, and it adds both the source and test jars to the classpath, as it should. Can someone help us here with either how to get the aggregator pom to refer to the local repostory rather than to the source directory, or with how to get the aggregator pom to properly refer to the test directory? -- View this message in context: http://www.nabble.com/Aggregator-pom-fails%2C-but-modules-work-tp21882332p22163774.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
