You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Peter Klügl (JIRA)" <de...@uima.apache.org> on 2016/07/20 13:17:20 UTC

[jira] [Created] (UIMA-5021) Cas Editor cannot import imported type system from classpath of selected type system

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)

Re: [jira] [Created] (UIMA-5021) Cas Editor cannot import imported type system from classpath of selected type system

Posted by Peter Klügl <pe...@averbis.com>.
Taking a step back:

I think this should not be a problem at all if not someone repackaged 
the plugins in a different feature, or uses the plugins without the feature.

The feature also contains the descriptor editor plugin which depends on 
jdt.core already, of course. So the actual package we distribute (the 
feature) already has the dependency. If someone want to install the CAS 
Editor right now, it would not work without fulfilling the dependency.

I also assume that there not so many users of special CAS Editors 
integrated in other RCP applications. There are very few bug reports and 
feature requests (and I know most of the reporters).

Summary: I think it should be OK to add the dependency.

Best,

Peter


Am 21.07.2016 um 17:27 schrieb Peter Kl�gl:
> 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)



Re: [jira] [Created] (UIMA-5021) Cas Editor cannot import imported type system from classpath of selected type system

Posted by Peter Klügl <pe...@averbis.com>.
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)


Re: [jira] [Created] (UIMA-5021) Cas Editor cannot import imported type system from classpath of selected type system

Posted by Marshall Schor <ms...@schor.com>.
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)
>


Re: [jira] [Created] (UIMA-5021) Cas Editor cannot import imported type system from classpath of selected type system

Posted by Peter Klügl <pe...@averbis.com>.
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)