[jira] [Created] (UIMA-2953) jcasgen-maven-plugin needs to support patterns

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

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

             Summary: jcasgen-maven-plugin needs to support patterns
                 Key: UIMA-2953
                 URL: https://issues.apache.org/jira/browse/UIMA-2953
             Project: UIMA
          Issue Type: Improvement
            Reporter: Richard Eckart de Castilho


With the old JCasGenPomFriendly class in uimaFIT, it was possible to select the descriptors for which JCas wrappers should be generated using a wildcard pattern:

{noformat}
<configuration>
  <mainClass>org.apache.uima.fit.util.JCasGenPomFriendly</mainClass>
  <arguments>
    <argument>file:${project.basedir}/src/test/resources/org/apache/uima/fit/type/**/*.xml</argument>
    <argument>${project.build.directory}/generated-sources/jcasgen</argument>
  </arguments>
  <classpathScope>test</classpathScope>
</configuration>
{noformat}

With the current jcasgen-maven-plugin, only a single descriptor file is possible. This is quite inconvenient for users. At least there should be the same possibility of specifying a wildcard pattern as in the JCasGenPomFriendly. Even better would be, to combine that with the commonly used include/exclude pattern used in many Maven plugins, e.g.

{noformat}
<plugin>
  <groupId>org.apache.uima</groupId>
  <artifactId>jcasgen-maven-plugin</artifactId>
  <executions>
    <execution>
      <goals>
	<goal>generate</goal>
        <configuration>
          <typeSystemIncludes>
            <typeSystemInclude>src/main/resources/types/**/*.xml</typeSystemInclude>
          </typeSystemIncludes>
          <typeSystemExcludes>
            <typeSystemExclude>src/main/resources/types/**/nojcas/*.xml</typeSystemInclude>
          </typeSystemExcludes>
        </configuration>
      </goals>
    </execution>
  </executions>
</plugin>
{noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira