in my case, I was running mvn clean install on uimaj-core (by itself); the test
phase was somehow finding some v2 tests even though I had v3 checked out, and my
windows file explorer (and eclipse) both showed no such test files were in the
working dir.
I probably made some foolish kind of error
On 17. Jan 2020, at 18:02, Marshall Schor wrote:
>
> I guess a moral of this story is to not do git switch between uima v2 and v3,
> but instead do something that erases the local working directory, and then
> does
> a checkout again.
When I do a switch between v2 and v3, I always run a "mvn
While working on UIMA-6128, I at one point switched my local repo to master,
made a new branch from this, and merged into that the v2 master, to pick up the
6128 change.
To my surprise, when I tried running a test build on uimaj-core (which had the
changes), the test failed, running 2 test
