On 31.05.2017, at 17:16, Marshall Schor <[email protected]> wrote: > > I think not a blocker: this release includes uimaj-core at version 2.10.0, and > other components in extras/ at the 2.10.0 level. > > The README doesn't mention this, and says "uimaFIT requires ... UIMA 2.9.0 or > higher ... "
*sigh*... looks like for some reason I set back all references to uimaj-core 2.9.0 (as we had discussed on the list) *except* the variable in the POM. No idea how that slipped through. I guess that means cancelling again and doing an RC2. But before that I would like to resolve the discussion around the API reports and whether or not the new API plugin that we are using does the same kind of semantic versioning checks as the semver plugin did. I had somehow assumed that it did, but looking at the documentation now, it seems that these checks are turned off by default: https://siom79.github.io/japicmp/MavenPlugin.html breakBuildBasedOnSemanticVersioning is per default set to false. I thought that the semver plugin had been replaced because the new one provides better reports. But really, these reports are tedious to read. Shouldn't we enable "breakBuildBasedOnSemanticVersioning" to get warned again of cases were we increase the version number less than semantic versioning would mandate? Cheers, -- Richard
