You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/03/29 06:07:48 UTC

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

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

Brett Porter moved MOJO-225 to MCHANGES-27:
-------------------------------------------

    Fix Version:     (was: 2.0)
                 2.0
      Component:     (was: changes)
       Workflow: jira  (was: Maven New)
            Key: MCHANGES-27  (was: MOJO-225)
        Project: Maven 2.x Changes Plugin  (was: Mojo)

> 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
>      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