jcasgen not running in process-test-resources phase

[GoogleCodeExporter]

it used to run before the parent project was introduced and now it doesn't.  
This means that the first time someone checks out the project the jcasgen files 
need to be manually generated.  This needs to be fixed so that they are 
generated the first time "mvn test" is executed.

Original issue reported on code.google.com by pvogren@gmail.com on 7 Jul 2010 at 11:23

[GoogleCodeExporter]

Ah. I duplicated this in issue 37. The generator was still called, but the 
search pattern for the descriptors was pointing to the wrong location. It 
should be fixed now. I tested with a fresh check out on OS X. Please test on 
Windows.

Original comment by richard.eckart on 8 Jul 2010 at 9:57

[GoogleCodeExporter]

Issue 37 has been merged into this issue.

Original comment by richard.eckart on 8 Jul 2010 at 3:08

[GoogleCodeExporter]

I tested it on Windows.  Works fine.  Thanks.

Original comment by pvogren@gmail.com on 8 Jul 2010 at 11:17

• Changed state: Done

[GoogleCodeExporter]

Original comment by richard.eckart on 10 Jan 2011 at 4:18

• Changed state: Closed

[GoogleCodeExporter]

I'm not sure why the status is "Closed".  It's still showing up in the default 
list of open issues.  So, I am changing the status to fixed.

Original comment by pvogren@gmail.com on 12 Jan 2011 at 7:28

• Changed state: Fixed

[GoogleCodeExporter]

I was playing around with Eclipse Mylyn + GoogleCode and tried to imitate the 
Bugzilla/Jira lifecycle where a bug arrives at the end of its life-cycle when 
it's "closed". I usually have issues on my radar until they reach that state. 
However, I soon realized that Google Code does not offer a "resolution" field 
like Jira and Bugzilla offer which preserves the what actually happened (fixed, 
invalid, won't fix, etc). When I noticed that I removed the "Closed" resolution 
again from uimaFIT, but obviously forgot to re-set the issue to "fixed".

Original comment by richard.eckart on 13 Jan 2011 at 7:59