maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Derricutt (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MCHANGES-139) Add support for a prefix string in Jira version numbers
Date Wed, 26 Nov 2008 02:03:19 GMT

     [ http://jira.codehaus.org/browse/MCHANGES-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Derricutt closed MCHANGES-139.
-----------------------------------

    Resolution: Fixed

After looking through the code and experimenting, it seems I can already do this with setting
<version/>.

> Add support for a prefix string in Jira version numbers
> -------------------------------------------------------
>
>                 Key: MCHANGES-139
>                 URL: http://jira.codehaus.org/browse/MCHANGES-139
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Improvement
>          Components: jira-report
>    Affects Versions: 2.1
>            Reporter: Mark Derricutt
>            Priority: Minor
>
> Due to Jira's lack of support for versions at the component level or sub-projects, a
lot of people tend to encode a components name inside a JIRA version string, such as "Admin
Tool 1.2", or "Product X Invoicing Module 1.4".
> It would be good if the JiraMojo could be configured to pass in "prefix" to JiraReportGenerator,
this would default to either ${project.artifactId} or ${project.name} (preference would be
the later) but configurable in the plugins <configuration/> element.
> This would allow the jira report to support those companies who can't, or would prefer
to stick to a single JIRA project.

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

        

Mime
View raw message