[AVRO-647] Break avro.jar into avro.jar, avro-dev.jar and avro-hadoop.jar

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Component/s: java
• Assignee: Scott Carey
• Reporter: Scott Carey
• Created: 01/Sep/10 01:25
• Updated: 12/Mar/11 00:32
• Resolved: 16/Dec/10 00:40

Description

Our dependencies are starting to get a little complicated on the Java side.

I propose we build two (possibly more) jars related to our major dependencies and functions.

1. avro.jar (or perhaps avro-core.jar)
This contains all of the core avro functionality for using avro as a library. This excludes the specific compiler, avro idl, and other build-time or development tools, as well as avro packages for third party integration such as hadoop. This jar should then have a minimal set of dependencies (jackson, jetty, SLF4J ?).

2. avro-dev.jar
This would contain compilers, idl, development tools, etc. Most applications will not need this, but build systems and developers will.

3. avro-hadoop.jar
This would contain the hadoop API and possibly pig/hive/whatever related to that. This makes it easier for pig/hive/hadoop to consume avro-core without circular dependencies.

Issue Links

• is related to: AVRO-159 maven-avro-plugin: Allow maven builds to use avro
• is related to: AVRO-572 Create a Maven plugin goal and Ant task to generate an avpr file from a avdl file
• relates to: AVRO-545 Move mapreduce bindings out of avro jar
• relates to: HBASE-3394 Generate Avro Java files at compile time
• relates to: AVRO-714 New Java build: Documentation

Sub-Tasks

• Move mapreduce bindings out of avro jar: Closed
• maven-avro-plugin: Allow maven builds to use avro: Closed