Hi Doug, That certainly helps a lot. Though one would still need extra code to pull out the required schema files from a jar into that imports directory prior to code generation. And one would need to track these avro dependencies manually. It would be great if the avro-maven-plugin could have configuration items specified like "com.example:common" and those artifacts would be searched for compiled avro types using something like the code I posted earlier in addition to the normal parser name resolution.
-Steven Willis > -----Original Message----- > From: Doug Cutting [mailto:[email protected]] > Sent: Tuesday, December 11, 2012 5:55 PM > To: [email protected] > Subject: Re: How to handle schema dependencies > > On Tue, Dec 11, 2012 at 1:42 PM, Steven Willis <[email protected]> > wrote: > > It would be nice if during schema parsing we could specify a > classpath > > to be used for dynamic lookup of external schemas > > Does AVRO-1188 (included in Avro 1.7.3) help here? > > https://issues.apache.org/jira/browse/AVRO-1188 > > This permits one to specify directories of schemas to import to Avro > Maven executions. > > Doug
