On 7/1/2013 5:02 PM, Marshall Schor wrote: > On 7/1/2013 3:45 PM, Richard Eckart de Castilho wrote: >> I believe it would in principple be much simpler just to skip the imported >> type systems and rely on the pattern mechanism. We don't really have to >> maintain backwards compatibility here, because this is going to be the first >> release. >> >> How about skipping imported systems and later - if necessary - add an option >> to include imported types? >> >> A complicating factor is the limited API of jcasgen itself though. > That's OK with me - that will simplify the jcasgen maven plugin. I think the > best way to implement this is to add an internal-use-only parameter to the > JCasgen tool that does the right thing, something like noting which types come > from the top level imports, and only generating those. > > I'll take a look at doing that. On reflection, I realize I'm confused about the motivation for having multiple inputs for the maven jcasgen plugin, and I've posted a query about this on that Jira.
-Marshall > > -Marshall > >> -- Richard >> >> Am 01.07.2013 um 21:34 schrieb "Marshall Schor (JIRA)" <[email protected]>: >> >>> [ >>> https://issues.apache.org/jira/browse/UIMA-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel >>> ] >>> >>> Marshall Schor updated UIMA-2958: >>> --------------------------------- >>> >>> Description: >>> Add an option, perhaps something like <skipGenerationForImportedTypes>, >>> which if true (not the default) would only generate those types which were >>> defined directly (that is, not via an import) in the set of type system >>> descriptors specified as input for this plugin. >
