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, 14 Dec 2010 03:28:01 GMT

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

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

checkstyle just needed a minor tweak, that works now.  In the next patch that is bound to
the maven 'validate' phase.

RAT already works, via "mvn rat:check", because we inherit from the Apache master pom which
sets that up for us.   We probably want to run that in the validate phase too once it is configured
right -- it fails now due to several files that we should fix or ignore.

After the migration, I validated that no java files were forgotten.  The next patch will include
'svn delete java/lang/src' .   We can remove the ivy stuff and bits of the ant script we no
longer want in another ticket.  This is also not wired up to the base project build.sh yet,
but that should be an easy follow-on.

Other follow-ons: 
Document the build process in the wiki.
Ensure that javadoc/source jars are created in a release build.

If this checks out and we have a +1 or two I'll commit it.

> 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
>             Fix For: 1.5.0
>
>         Attachments: AVRO-647.patch, AVRO-647.patch, migrateAvro.sh
>
>
> 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