You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2012/05/11 20:46:56 UTC

[jira] [Assigned] (UIMA-1176) JCasGen shouldn't generate types for imported type systems (or at least it should be an option)

     [ https://issues.apache.org/jira/browse/UIMA-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor reassigned UIMA-1176:
------------------------------------

    Assignee: Marshall Schor
    
> 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
>            Assignee: Marshall Schor
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira