[ http://jira.codehaus.org/browse/MOJO-225?page=comments#action_55955 ]
Allan Ramirez commented on MOJO-225:
------------------------------------
Hi,
Try this:
In your <reporting> section specify the goal you want to execute.
{code:xml}
<reporting>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>changes-maven-plugin</artifactId>
<executions>
<execution>
<id>changes-report</id>
<goals>
<goal>changes-report</goal>
</goals>
<configuration>
<!-- config the plugin here -->
</configuration>
</execution>
</execution>
</executions>
</plugin>
</plugins>
</reporting>
{code}
> Add 'disable jira' flag
> -----------------------
>
> Key: MOJO-225
> URL: http://jira.codehaus.org/browse/MOJO-225
> Project: Mojo
> Type: New Feature
> Components: changes
> Versions: 2.0-beta-1
> Reporter: Mike Perham
> Fix For: 2.0
>
>
> When the changes report is configured to run as part of the site build, the
> JIRA report also runs. I don't know why this is but I assume the maven
> reporting subsystem has a way to determine the report goals associated with a
> report plugin. At any rate, the project might not use or want a JIRA report
> so we should provide some flag that tells maven to run the changes report but
> don't run the jira report.
--
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
