On 10 mars 2011, at 00:29, Stefan Seelmann wrote:

On Wed, Mar 9, 2011 at 7:30 PM, Pierre-Arnaud Marcelot <> wrote:
FYI, I could only get it to work with the following command line:
mvn package site

[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15:00.742s
[INFO] Finished at: Wed Mar 09 10:58:17 CET 2011
[INFO] Final Memory: 423M/757M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site (default-site) on project shared-integ: failed to get Reports: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.2:copy (copy) on project shared-integ: Error copying artifact from /Users/pajbam/Development/Apache/trunks/shared/ldap/extras/codec/target/classes to /Users/pajbam/Development/Apache/trunks/shared/integ/target/pluginDirectory/shared-ldap-extras-codec-1.0.0-M2-SNAPSHOT.jar -> [Help 1]

The problem is that the artifact (shared-ldap-extras-code in that
case) is within the reactor, so the maven-dependency-plugin expects
that the artifact can be found in the target folder. One idea I have
is to exclude the shared-integ module from default build, put it into
a profile and only activate it with the -Dintegration property. So
with a "mvn clean install -Dintegration" the integration test are
exectued. But with a "mvn site" the module is excluded and won't
complain any more. I think it would be acceptable to exclude
shared-integ from the site. WDYT?

Kind regards