On Tue, Sep 23, 2008 at 3:56 PM, Geoffrey Wiseman < [EMAIL PROTECTED]> wrote:
> Seems to be some weird interaction between the classpath and the site > plugin in a multimodule. Basically, I've got a structure somewhat like this > within some part of my project structure: > > model <- persistence <- service > > Model contains some domain model classes, but the tests contain a few > builders for model classes that help make tests easier to write. > Accordingly, the persistence module depends both on the model (main > artifact, compile scope) and the model tests (test classifier, test scope). > The service code relies on some of those model classes. > > When you run "mvn clean install" on the whole thing, it's fine. When you > run "mvn clean install site" on the whole thing, the service module doesn't > include the model main artifact (project or JAR) on the compile classpath, > and fails. If you run "mvn clean install site" on the service module alone, > it's fine. > > If I get a chance, I'll put together an example project. In the meantime, > I'll probably just put the builders in the main source tree for now - seems > to make the problem go away. > Simple example project using the terms in this email exhibits the same behavior. http://jira.codehaus.org/browse/MNG-3763 -- Geoffrey Wiseman
