I looked a little bit into that.
1) generating parquet files deployed to the repo
This plugin looks promising: http://mojo.codehaus.org/exec-maven-plugin/index.html
use "mvn exec:help -Ddetail=true -Dgoal=java" to get detailed help
example to execute a command in parquet-mr: "mvn -pl parquet-hadoop exec:java -Dexec.mainClass="parquet.hadoop.PrintFooter""
So you could attach the "java" goal to the "generate-resources" phases
http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_executions_Tag
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference

My idea is to add a module in parquet-mr that would generate a jar with the .csv and corresponding .parquet files in it.
That could be done with the exec:java goal as described above that would generate those files in the resources.
This way every time we deploy a jar to a repo we deploy as well the corresponding files.

2) generating files at test time
Another way would be to have a module in parquet-compatibility for each version of parquet we want to test against.
Each module would generate a file for this version. A separate module would try to read them all with the latest version.
This option might be easier.