ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Eckart de Castilho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CTAKES-283) Avoid duplicate generation of JCas classes
Date Sun, 26 Jan 2014 19:02:37 GMT

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

Richard Eckart de Castilho updated CTAKES-283:
----------------------------------------------

    Description: 
Various cTAKES modules run the jcasgen-maven-plugin to automatically generate JCas classes.
Because the type system definitions in these modules tend to import type system definitions
from the ctakes-type-system module and because currently cTAKES uses the old jcasgen-maven-plugin
from ClearTK, this leads to duplicate JCas classes being generated for the imported types.

This could be fixed by upgrading to the Apache UIMA jcasgen-maven-plugin. Because the new
version supports ANT-like include/exclude patterns, all individual calls to the plugin in
every module can be replaced by placing this in the ctakes root module plugins section.

{noformat}
<plugin>
  <groupId>org.apache.uima</groupId>
  <artifactId>jcasgen-maven-plugin</artifactId>
  <version>2.5.0</version>
  <executions>
    <execution>
      <goals><goal>generate</goal></goals>
      <configuration>
        <typeSystemIncludes>
          <typeSystemInclude>src/main/resources/org/apache/ctakes/**/types/TypeSystem.xml</typeSystemInclude>
        </typeSystemIncludes>
        <limitToProject>true</limitToProject>
      </configuration>
    </execution>
  </executions>
</plugin>
{noformat}


  was:
Various cTAKES modules run the jcasgen-maven-plugin to automatically generate JCas classes.
Because the type system definitions in these modules tend to import type system definitions
from the ctakes-type-system module and because currently cTAKES uses the old jcasgen-maven-plugin
from ClearTK, this leads to duplicate JCas classes being generated for the imported types.

This could be fixed by upgrading to the Apache UIMA jcasgen-maven-plugin:

{noformat}
<plugin>
  <groupId>org.apache.uima</groupId>
  <artifactId>jcasgen-maven-plugin</artifactId>
  <version>2.5.0</version>
  <executions>
    <execution>
      <goals><goal>generate</goal></goals>
      <configuration>
        <typeSystemIncludes>
          <typeSystemInclude>src/main/resources/org/apache/ctakes/padtermspotter/types/TypeSystem.xml</typeSystemInclude>
        </typeSystemIncludes>
        <limitToProject>true</limitToProject>
      </configuration>
    </execution>
  </executions>
</plugin>
{noformat}



> Avoid duplicate generation of JCas classes
> ------------------------------------------
>
>                 Key: CTAKES-283
>                 URL: https://issues.apache.org/jira/browse/CTAKES-283
>             Project: cTAKES
>          Issue Type: Improvement
>            Reporter: Richard Eckart de Castilho
>
> Various cTAKES modules run the jcasgen-maven-plugin to automatically generate JCas classes.
Because the type system definitions in these modules tend to import type system definitions
from the ctakes-type-system module and because currently cTAKES uses the old jcasgen-maven-plugin
from ClearTK, this leads to duplicate JCas classes being generated for the imported types.
> This could be fixed by upgrading to the Apache UIMA jcasgen-maven-plugin. Because the
new version supports ANT-like include/exclude patterns, all individual calls to the plugin
in every module can be replaced by placing this in the ctakes root module plugins section.
> {noformat}
> <plugin>
>   <groupId>org.apache.uima</groupId>
>   <artifactId>jcasgen-maven-plugin</artifactId>
>   <version>2.5.0</version>
>   <executions>
>     <execution>
>       <goals><goal>generate</goal></goals>
>       <configuration>
>         <typeSystemIncludes>
>           <typeSystemInclude>src/main/resources/org/apache/ctakes/**/types/TypeSystem.xml</typeSystemInclude>
>         </typeSystemIncludes>
>         <limitToProject>true</limitToProject>
>       </configuration>
>     </execution>
>   </executions>
> </plugin>
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message