[ 
https://issues.apache.org/jira/browse/UIMA-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631614#action_12631614
 ] 

Tong Fin commented on UIMA-1176:
--------------------------------

I think there are 2 ways to use "import" in UIMA descriptors:
1. easy to read the descriptor and easy to maintain and share across the 
descriptors
2. use someone else descriptor 

Adam's use-case is the case#2 and I think most people use case#1 more often 
than cas#2.
If we support this new feature request, I suggest that we make it as an 
"option" with the current behavior as the "default".

There are many use-cases to think about. For example:

<analysis engine descriptor>
    <import localtion="my_non_shared_type_system.xml">
</analysis engine descriptor>
<descriptor for my_non_shared_type_system>
   <import location="someone_else_shared_type_system.xml>
</descriptor for my_non_shared_type_system>

<analysis engine descriptor>
    <import localtion="someone_else_shared_type_system..xml">
</analysis engine descriptor>



> JCasGen shouldn't generate types for imported type systems (or at least it 
> should be an option)
> -----------------------------------------------------------------------------------------------
>
>                 Key: UIMA-1176
>                 URL: https://issues.apache.org/jira/browse/UIMA-1176
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Eclipse plugins, Tools
>    Affects Versions: 2.3
>            Reporter: Adam Lally
>
> Our project reuses a common type system that we got from a different source.  
> The common type system descriptor is imported into our main type system 
> descriptor.  The common type system has its own JCas types, in a jar file.  
> When we generate JCas types for our main type system descriptor, it currently 
> generates all of the classes for all of the imported type systems as well.  
> We don't want this behavior, so we have to manually go through and delete 
> those classes.
> I think JCasGen should only generate types for the type system descriptor 
> that you run it on, not on imported type system descriptors.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to