[
https://issues.apache.org/jira/browse/UIMA-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12631628#action_12631628
]
Adam Lally commented on UIMA-1176:
--
Well, how about this: If my main type system descriptor imports another type
system descriptor that is not in the same Eclipse project, then JCasGen should
not generated classes for those imported types.
When the type system descriptors are in different projects, I think it is very
likely that they represent separate modules of the type system that are
maintained on their own. I want to keep the JCas classes for each module in
the same project (or jar) as the type system descriptor for that module. If I
import this module into another type system, I don't want JCasGen making
additional copies of my JCas classes into every place where I use that module.
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.
