Cancelling due to the problem reported by Eddie Epstein.
Will fix examples and redo the RC
Thanks to all who spent time testing!
Jerry
Damn, I now remember this exact issue biting me before. I'd modified my old
release script but
unfortunately lost it when my disk drive died. Will update the new one to
make sure this is always
tested with every release.
Jerry
On Sat, Jan 6, 2018 at 6:55 PM, Eddie Epstein wrote:
> - downloaded
OK, agree that the README should not say to always use -U when building.
However, it should say that
when strange errors occur during a build, running with -U *may* help. Eddie
ran into such problem
and suggested documentation change to help users remedy the situation. The
point is that it is not
Hi,
I think that the answer depends on the meaning of the question :-)
It *is* supported if the question is:
- step 1, 2, 3, 4 + then starting up a new pipe line in a new class loader.
It is *not* supported, (even in v2) if the question is:
- step 1, 2, 3, 4 where the JCas classes were loa
On 07.01.2018, at 06:06, Marshall Schor wrote:
>
> This only works when the different type definitions for type T keep the slots
> in
> the same order, with no omissions.
> (The JCas initialization for a new type system checks this.) For example,
> valid
> definions for type T would be
> T w
