You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 22:58:36 UTC

[jira] (MPCHANGELOG-59) Filter support for changelog status

     [ https://jira.codehaus.org/browse/MPCHANGELOG-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MPCHANGELOG-59.
-------------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> Filter support for changelog status
> -----------------------------------
>
>                 Key: MPCHANGELOG-59
>                 URL: https://jira.codehaus.org/browse/MPCHANGELOG-59
>             Project: Maven 1.x Changelog Plugin
>          Issue Type: Improvement
>            Reporter: Nick Matthews
>
> The ability to filter different paths of the repository tree would be useful.
> For example, at a certain level in our project tree, we have a component/ tree, which has several sub-parts.
> Each of these sub-elements have a source, test and doc branch.
> project1/A/source
> project1/A/test
> project1/A/doc
> project1/B/source
> project1/B/test
> project1/B/doc
> project1/C/source
> project1/C/test
> project1/C/doc
> project2/A/source
> project2/A/test
> project2/A/doc
> My maven project consists of project1, which has components A,B, and C.
> It would be nice to have filters to exclude checkins to the test and doc directories. 
> Also, if componentC contains deprecated code, or a highly experimental branch, we don't necessarily want to include checkins to this either.
> In these cases, a filter would be very useful, to prevent spamming the changlist and file list with checkins to files outside of the main release.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)