Hi list,
I found a really strange behavior with the following setup:
We're creating a site for distribution with our product (packaged in a
distribution zip file). We're creating the site as a part of our
multi-project build and the site:site mojo is bound to the packaging
phase.
This is the configuration of our site generation:
========================================= SNIPPET BEGIN
[...]
<plugin>
<artifactId>maven-site-plugin</artifactId>
<version>2.0-beta-6</version>
<executions>
<execution>
<goals><goal>site</goal></goals>
<phase>package</phase>
</execution>
</executions>
</plugin>
[...]
<reporting>
<excludeDefaults>true</excludeDefaults>
<plugins>
<plugin>
<artifactId>maven-project-info-reports-plugin</artifactId>
<reportSets><reportSet /></reportSets>
</plugin>
<plugin>
<artifactId>maven-changes-plugin</artifactId>
<version>2.0-beta-3</version>
<reportSets>
<reportSet>
<reports>
<report>changes-report</report>
</reports>
</reportSet>
</reportSets>
<configuration>
<xmlPath>src/changes/changes.xml</xmlPath>
</configuration>
</plugin>
</plugins>
</reporting>
[...]
========================================= SNIPPET END
This works perfectly if a lifecycle-phase >= package is invoked in the
site project.
I our case we're invoking the install phase in the parent module. The
site-generation is being invoked with the but *without the generation
of the changes report*. Again, this is not the case if we're invoking
install in the site module itself. The changes report is generated
without a problem.
I've attached a complete testcase to this mail.
Any help would be appreciated!
Francois
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
