If the team agrees that separate packages for each language makes sense, I will happily invest the time and effort to make it a reality. Even though I was <dreaming>, I didn't mean to imply it's too large of a job to do. It was more of an admission that this is my dream and might not be shared by everyone (or anyone for that matter). :)
Have a good weekend everyone. -Matt On Fri, Oct 16, 2009 at 3:11 PM, Matt Massie <[email protected]> wrote: > > <dreaming> > > For example, have the following top-level directories: "java", "python", > "c++", "c", "shared". The shared directory would be for dropping common > test cases (e.g. schemas, data files, etc) to ensure interop. Instead of > having 'ant' as the top-level task master, we'd have a simple '/bin/sh' > script called say 'avro_build' which would be used for testing all > implementations, generating all documentation and lastly generating packages > for a release. > > $ ./avro_build.sh test > $ ./avro_build.sh release > $ ls release_dir > avro-java-x.x.x.tar.gz > pyavro-x.x.x.tar.gz > avro-c++.x.x.x.tar.gz > > </dreaming> > > -Matt > > >> >> Doug >> > >
