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

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

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

Richard Eckart de Castilho resolved UIMA-4131.
----------------------------------------------
    Resolution: Fixed

Checked in OS X and Windows. Looks ok.

> 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)