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

Posted to dev@uima.apache.org by "Peter Klügl (JIRA)" <de...@uima.apache.org> on 2014/09/30 16:11:34 UTC

[jira] [Commented] (UIMA-4001) Ruta: jira report for fix version instead of component

    [ https://issues.apache.org/jira/browse/UIMA-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153186#comment-14153186 ] 

Peter Klügl commented on UIMA-4001:
-----------------------------------

It is easy to apply these chnages, but after thinking about this issue, I'd rather keep the component constraint. The issues should specify the ruta component, otherwise we could just skip it all the time. The release manager should investigate the issues with the fixVersion also without the component filter.

> Ruta: jira report for fix version instead of component
> ------------------------------------------------------
>
>                 Key: UIMA-4001
>                 URL: https://issues.apache.org/jira/browse/UIMA-4001
>             Project: UIMA
>          Issue Type: Task
>          Components: ruta
>    Affects Versions: 2.2.0ruta
>            Reporter: Peter Klügl
>            Assignee: Peter Klügl
>            Priority: Minor
>
> The generated jira report should maybe depend on "fix version" alone. Investigate if there might occur problems if an issue of another component uses an additional ruta "fix version" in order to point out fixed functionality of the ruta dependencies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)