avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Carey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-647) Break avro.jar into avro.jar, avro-dev.jar and avro-hadoop.jar
Date Tue, 21 Sep 2010 22:19:33 GMT

    [ https://issues.apache.org/jira/browse/AVRO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913281#action_12913281
] 

Scott Carey commented on AVRO-647:
----------------------------------

Yes, the path I have gone down so far has split the classes in packages amongst the jars.
 Moving Requestor means moving several things that go with it.  There is no way at this time
to split by package in most places.

Having it be easier in a few places would be nice however.  The list of 'svn cp' s to run
before applying the patch is getting very messy!  If there are a few places where an entire
package can move save for one or two classes, it might be worthwhile to move them.    specific/reflect/generic
are going to be split no matter what as far as I can tell -- and rightfully so at this time.

> Break avro.jar into avro.jar, avro-dev.jar and avro-hadoop.jar
> --------------------------------------------------------------
>
>                 Key: AVRO-647
>                 URL: https://issues.apache.org/jira/browse/AVRO-647
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>            Reporter: Scott Carey
>            Assignee: Scott Carey
>
> 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. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message