On the substance of the original problem: user runs 'mvn site:site'
site:site finds javadoc and checkstyle, trigger a forked lifecycle to generate sources. In this particular case, 'generate-sources' in module 'b' depends on running out through 'process-classes' in module 'a'. b has a compile-scope dependency on agroup:aartifact:aversion:wsdl. Is the lifecycle calculator supposed to figure this out? It has no way to tell which execution in 'a' produces agroup:aartifact:aversion:wsdl, so it has no way to tell that 'process-classes' is going to be required. However, adding 'process-classes' to the top-level command line doesn't help, apparently because it doesn't travel from the initial execution plan to the forked execution plan. Once you have the fix I made today, you can get around this by running 'mvn install' to stuff the wsdl artifact into the local repo before running site:site. But if the intent is to avoid this requirement, how is it supposed to work? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
