Thank you for doing this.
I think splitting the code is fine and will help coding.
Please look at:
http://www.tutorialspoint.com/maven/maven_quick_guide.htm
The maven build lifecycle has 23 phases, one is generate-resources (can
be used to generate java from gen, cup, and lex files) and another is
process-resources (to copy source files). So we can use antrun in
generate-resources to generate and place java code in some directory and
copy the rest (in process-resources) into the same directory.
Leonidas
On 06/18/2013 03:53 PM, Karthik Kambatla wrote:
For the mavenization, I am planning to split the project into three
sub-projects/modules - one each for the type of files. I believe this will
help us maintain the code better in the longer run. Please comment if you
think of any other organization might suit better.
Also, I was wondering if anyone is working on or thinking of any other kind
of code re-organization. If any work is underway, it might be nice to take
care of it before the move.
Thanks
Karthik
PS: Have been starving this for a while now, want to take care of this at
the earliest now.
.
