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