You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Mike Perham (JIRA)" <ji...@codehaus.org> on 2006/04/04 01:46:44 UTC

[jira] Closed: (MCHANGES-27) Add 'disable jira' flag

     [ http://jira.codehaus.org/browse/MCHANGES-27?page=all ]
     
Mike Perham closed MCHANGES-27:
-------------------------------

     Assign To: Mike Perham
    Resolution: Fixed

Reports can now be excluded by defining <reportSets>

> Add 'disable jira' flag
> -----------------------
>
>          Key: MCHANGES-27
>          URL: http://jira.codehaus.org/browse/MCHANGES-27
>      Project: Maven 2.x Changes Plugin
>         Type: New Feature

>     Reporter: Mike Perham
>     Assignee: 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