[MSITE-497] Dependencies not included classpath for multi-level projects when forking reporting

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Not A Problem
• Affects Version/s: 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
• Assignee: Olivier Lamy
• Reporter: Anders Hammar
• Created: 24/Aug/10 14:21
• Updated: 11/Sep/10 16:12
• Resolved: 11/Sep/10 16:10

Description

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

Issue Links

• duplicates: MNG-4795 [regression] Dependencies in forked reactor projects are not resolved when aggregator bound to lifecycle forks