You may be abusing 'src' and 'test.' Do you get the same problem if you
rename the sub-projects 'dir1' and 'dir2?' Have you considered something
like the shitty-maven-plugin? Google for 'maven integration testing.'
klimane wrote:
I have the following project structure:
ProjectA
pom.xml [aggregator of the other two]
src
pom.xml
test
pom.xml
When I run the test build by itself either from the test directory or by
modifying the aggregator pom to exclude the src module and only include the
test module, it works. However, when I run a build on the aggregator pom
(with the aggregator pom including both src and test modules), the test
module fails at compilation, stating that it can't find a class that is part
of the src build. The test/pom.xml has the src artifact as a dependency.
Also, I have this pattern working in other projects. I'm just wondering if
anyone has any suggestions or if anyone has seen this type of behaviour
before.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
