Uploaded image for project: 'Avro'
  1. Avro
  2. AVRO-647

Break avro.jar into avro.jar, avro-dev.jar and avro-hadoop.jar


    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5.0
    • Component/s: java
    • Labels:


      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.


        1. migrateAvro.sh
          8 kB
          Scott Carey
        2. AVRO-647.patch
          51 kB
          Scott Carey
        3. AVRO-647.patch
          45 kB
          Scott Carey
        4. AVRO-647.patch
          43 kB
          Scott Carey
        5. migrateAvro.sh
          8 kB
          Scott Carey

          Issue Links



              • Assignee:
                scott_carey Scott Carey
                scott_carey Scott Carey
              • Votes:
                0 Vote for this issue
                5 Start watching this issue


                • Created: