Not critical
Am 31.03.2016 um 00:31 schrieb Marshall Schor:
> I'm leaning toward thinking it isn't critical...
>
> What do others think?
>
> -Marshall
>
> On 3/29/2016 3:52 PM, Richard Eckart de Castilho wrote:
>> Hm, ok good to know. Sorry I didn't notice that before.
>>
>> The question is: is it a critical issue requiring a third RC?
>>
>> -- Richard
>>
>>> On 29.03.2016, at 21:49, Marshall Schor <[email protected]> wrote:
>>>
>>> I think I found the problem.
>>>
>>> It seems jira reporting fails if the "component" field is blank, or doesn't
>>> include uimaFIT.
>>>
>>> I changed these 3 Jiras to include those, and now the issues-fixed report
>>> includes them.
>>>
>>> -Marshall
>>>
>>> On 3/29/2016 10:33 AM, Richard Eckart de Castilho wrote:
>>>> Indeed.
>>>>
>>>> However, I don't see why they are missing.
>>>>
>>>> The Jira version ID is correctly set in the POM to: 12324057
>>>>
>>>> Searching under that ID in Jira yields the missing issues:
>>>>
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310570&version=12324057
>>>>
>>>> I also just did a local rebuild of the 2.2.0 sources with the release
>>>> profile activated to regenerate the report. It still does not include the
>>>> issues.
>>>>
>>>> Did you have such problems in the past?
>>>>
>>>> Best,
>>>>
>>>> -- Richard
>>>>
>>>>> On 29.03.2016, at 16:12, Marshall Schor <[email protected]> wrote:
>>>>>
>>>>> I see https://issues.apache.org/jira/browse/UIMA-4867 as a uimaFIT 2.2.0
>>>>> issue,
>>>>> but don't see it in the issues fixed list?
>>>>>
>>>>> also, https://issues.apache.org/jira/browse/UIMA-3869 not in issues fixed
>>>>> also, https://issues.apache.org/jira/browse/UIMA-4706
>>>>>
>>>>> -Marshall
