There is a way to do this. If you include the schema directory you have defined as a resource in your JAR, project2 can then depend on an artifact (project1). Once you've included that dependency, we're using the maven-dependency-plugin's goal of "unpack-dependencies" to extract those IDL files into a known directory. Once they've been extracted, you can depend on them at compile time and then delete that directory post generate-sources stage in your build.

On Mon, Apr 07, 2014 at 05:09:18PM +0000, renjith varma wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB