The command line from a new svn checkout works for me. The command line on the Eclipse version (running a command line, not from Eclipse, but in the files used by the Eclipse workspace), failed, the same way.
I went into Eclipse, and saw that the generated files were there, under target/generated-sources/jcasgen. I right-clicked that file, and told Eclipse to use that as a source file. (There's some automated way to do this so this step should not be needed, I think. We have similar things with the main uimaj-sdk build - it generates some sources, but they are automatically seen by Eclipse). That made it start to work. -Marshall On 12/12/2012 4:19 PM, Richard Eckart de Castilho (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/UIMA-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530340#comment-13530340 > ] > > Richard Eckart de Castilho commented on UIMA-2470: > -------------------------------------------------- > > The uimaFIT artifact probably has errors because the JCas classes for the > test types have not been generated during the import. Select "Run as -> Maven > test" once on the project, then refresh it, possibly select "Maven -> Update > project". After that, the JCas classes should have been generated and the > generated sources folder should have been added to the Eclipse project. The > command-line build runs just fine for me ouf of the box. > > The module folders are in mixed-case in the SVN and do currently not reflect > the artifact names. We can fix that later. > >> Donation of uimaFIT >> ------------------- >> >> Key: UIMA-2470 >> URL: https://issues.apache.org/jira/browse/UIMA-2470 >> Project: UIMA >> Issue Type: Task >> Components: Sandbox >> Reporter: Richard Eckart de Castilho >> Assignee: Marshall Schor >> Attachments: uimaFIT-grant-staging-rev-919.zip >> >> >> Donation of uimaFIT. >> uimaFIT provides Java annotations for describing UIMA components which can >> be used to directly describe the UIMA components in Java code without the >> need for traditional UIMA XML descriptors. This greatly simplifies >> refactoring a component definition (e.g., changing a configuration parameter >> name). uimaFIT also makes it easy to instantiate UIMA components without >> using XML descriptor files by providing convenient factory methods. This >> makes uimaFIT an ideal library for testing UIMA components because the >> component can be easily instantiated and invoked without requiring a >> descriptor file to be created first. uimaFIT is very useful in research >> environments in which programmatic/dynamic instantiation of UIMA pipelines >> can simplify experimentation. For example, when performing 10-fold >> cross-validation across a number of experimental conditions, it can be quite >> laborious to create a different set of descriptor files for each run, or >> even a script which generates such descriptor files. uimaFIT is type system >> agnostic and does not depend on (or provide) a specific type system. > -- > 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 >
