Dependencies not included classpath for multi-level projects when forking reporting -----------------------------------------------------------------------------------
Key: MSITE-497 URL: http://jira.codehaus.org/browse/MSITE-497 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 3.0-beta-1 Environment: Maven 3.0-beta-2 MacOS 10.6.4/Windows XP SP2 (or possibly SP3) Mac Java 1.6.0_20/SUN JDK 1.6.0_15 Reporter: Anders Hammar Priority: Critical Attachments: mvn3site-bug.zip, mvn_site_output.txt Executing "mvn site" on a multi-level project, where it hasn't been compiled first, makes the build fail because the dependencies can't be found (aren't included on the classpath). The attached test projects shows this. If run with Maven 2.2.1 it works fine, with Maven 3.0-beta-2 it fails. I'm also attaching a debug output of this. To recreate the issue on the project: mvn clean mvn site -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira