[jira] [Updated] (UIMA-2958) Do not follow references outside a project

["Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org>]

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

Richard Eckart de Castilho updated UIMA-2958:
---------------------------------------------

    Component/s: jcasgen-maven-plugin
    
> Do not follow references outside a project
> ------------------------------------------
>
>                 Key: UIMA-2958
>                 URL: https://issues.apache.org/jira/browse/UIMA-2958
>             Project: UIMA
>          Issue Type: Improvement
>          Components: jcasgen-maven-plugin
>            Reporter: Richard Eckart de Castilho
>             Fix For: 2.4.1SDK
>
>
> Rationale from UIMA-1176
> {quote}
> 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.
> {quote}
> One way to solve it as described in UIMA-2471
> {quote}
> Jg.main0 takes an array of string arguments. To make JCasGen limit the cover classes it generates to just those whose type definitions are contained in some directory (at any sub directory level), you pass 2 additional arguments in this array:
> 1) "-limitToDirectory" and then following that
> 2) the path to some directory. Currently this is typically set to a containing Eclipse project directory, for example, when JCasGen is called from the Component Descriptor Editor
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira