You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org> on 2014/11/29 22:21:12 UTC

[jira] [Created] (UIMA-4131) Limiting JCasGen scope fails in some cases

Richard Eckart de Castilho created UIMA-4131:
------------------------------------------------

             Summary: Limiting JCasGen scope fails in some cases
                 Key: UIMA-4131
                 URL: https://issues.apache.org/jira/browse/UIMA-4131
             Project: UIMA
          Issue Type: Bug
          Components: Tools
            Reporter: Richard Eckart de Castilho
            Assignee: Richard Eckart de Castilho
             Fix For: 2.7.0SDK


Consider the case where you have two projects:

* /my/project
* /my/project1

The first project contains a type descriptor which imports another type descriptor from the second project. 

When JCasGen is invoked with the option to limit generation to the first project, then JCas classes for the types imported from the second project are still generated. Why? Because "/my/project" is a prefix of "/my/project1". JCasGen thinks that "/my/project1" is within the scope of "/my/project".

This could be fixed by ensuring that paths terminate in a "/".




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)