Hi,
I was thinking about the same, but I found no reasonable solution yet. (I really do not want to introduce an extension point and an additional plugin implementing it.) Best, Peter Am 21.07.2016 um 17:11 schrieb Marshall Schor: > This is probably OK, but I wonder: > > Is there a fall-back or work-around for plain RCP applications? > > Can the approach be "conditional" if the dependency is present? > > -Marshall > > On 7/21/2016 9:08 AM, Peter Klügl wrote: >> Hi, >> >> >> are there any objections if the CAS Editor gets an dependency to >> org.eclipse.jdt.core (= Java IDE)? >> >> I want to enable the CAS Editor to resolve imports by name of type >> systems using the classpath of the project it is located in, or the >> maven dependencies. >> >> >> This would cause serious problems if the CAS Editor is used in plain RCP >> applications. >> >> >> Best, >> >> >> Peter >> >> >> >> Am 20.07.2016 um 15:17 schrieb Peter Klügl (JIRA): >>> Peter Klügl created UIMA-5021: >>> --------------------------------- >>> >>> Summary: Cas Editor cannot import imported type system from >>> classpath of selected type system >>> Key: UIMA-5021 >>> URL: https://issues.apache.org/jira/browse/UIMA-5021 >>> Project: UIMA >>> Issue Type: Bug >>> Components: CasEditor >>> Affects Versions: 2.8.1SDK >>> Reporter: Peter Klügl >>> Assignee: Peter Klügl >>> >>> >>> Cas Editor cannot import imported type system from classpath of selected >>> type system >>> >>> >>> >>> -- >>> This message was sent by Atlassian JIRA >>> (v6.3.4#6332)
