Move the JCas class to a separate artifact that the user may depend on but does not have to.
-- Richard > On 23.06.2018, at 23:54, Eddie Epstein <[email protected]> wrote: > > DUCC includes a default Job flow controller that uses one custom type. It > would be easy to change the FC code to use CAS rather than JCas API. The > bigger problem is that the JCas class is included in a DUCC "user" jar for > application code. Removing the JCas class will break existing user apps, > until the app is changed to provide the class. Is there a better solution? > Eddie
