On 12/27/2013 2:09 PM, Marshall Schor wrote: > Further investigation seems to show: > > 1) the Type info (bug, improvement, task, etc.) is not being produced by the > maven-changes-plugin version 2.9, although it is retrieved. This looks like a > bug in the plugin.
I submitted a Jira for this maven-changes-report issue: http://jira.codehaus.org/browse/MCHANGES-325 -Marshall > > 2) the fetching of information from Jira for the DUCC job has a message at the > beginning of the output trace, which says: (message truncated to 102400 > bytes). > So the fact that this implementation is fetching *all* Jira data for each > issue, > plus the large number of Jiras (> 300) may be producing more data than is > "allowed" by some part of this. I can't tell what is producing this > "truncated" > message, or why - it may be the logger? > > I think for DUCC we need to do something "manual", and disable automatic Jira > reporting for this first release. > > -Marshall > > > On 12/23/2013 6:56 PM, Marshall Schor wrote: >> The first change that starting getting things working was to switch to >> version >> 2.9 (from 2.8) of the maven-changes plugin. >> >> It now shows a bunch of results, but still isn't quite right... more >> debugging >> to come. >> >> -Marshall >> >> On 12/23/2013 5:18 PM, Marshall Schor wrote: >>> Whatever the issue is, it's also affecting the builds of uimaj, for >>> instance. >>> >>> I think a Jira upgrade is probably the cause of this... Still >>> investigating, >>> but other seasonal activities are causing some delay :-) >>> >>> -Marshall >>> On 12/23/2013 1:03 PM, Marshall Schor wrote: >>>> I'll take a look >>>> -M >>>> On 12/23/2013 12:41 PM, Jaroslaw Cwiklik wrote: >>>>> Yes, the source release "issues-fixed" is not right. Is this possibly a >>>>> bug >>>>> with the source assembly script? >>>>> If so, Marshall can you address this? >>>>> >>>>> >>>>> On Fri, Dec 20, 2013 at 12:24 AM, Marshall Schor <[email protected]> wrote: >>>>> >>>>>> Many of the Jira issues that are cited as part of this release are >>>>>> missing >>>>>> the >>>>>> "fixed in" field. >>>>>> >>>>>> If you go to the issues list (below) it shows 403 issues. >>>>>> >>>>>> If you go to >>>>>> https://issues.apache.org/jira/browse/UIMA/fixforversion/12324398 >>>>>> >>>>>> it only shows 227. The difference is caused (I think) by the missing >>>>>> "fixed in" >>>>>> field. >>>>>> >>>>>> The source-release's "issues fixed" shows only 6 issues ! Something went >>>>>> wrong >>>>>> here... (unless my browser is really messed up)... >>>>>> >>>>>> -Marshall >>>>>> >>>>>> >
