uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-1176) JCasGen shouldn't generate types for imported type systems (or at least it should be an option)
Date Fri, 11 May 2012 21:23:52 GMT

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

Marshall Schor commented on UIMA-1176:

I'm implementing this as follows:
It's based on the concept of being in the "same project" or not. If enabled, types defined
in descriptors which are not in the same project are skipped.

For non-eclipse environments, a directory path passed in serves as a surrogate for the project.

The skipping is only done if the type in question didn't undergo an "expansion" (more features)
because of type merging.  If the type to be "skipped" has been merged, then an error is reported
(only if this limiting of generation is enabled).

1) change the basic JCasGen to take additional parameters - a boolean specifying whether to
limit generation of non-locally defined Types.
2) change the CDE to add a check button under the JCasGen button on the type definition page,
to enable this limiting.
3) add a global, remembered (in preferences for the CDE) setting for this, and put it in both
the special UIMA menu and the UIMA preferences.  
4) make the automatic running of jcasgen (if selected) respect the global setting.
> 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


View raw message