avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Kimball (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AVRO-314) Allow Avro to publish to a local m2 repository
Date Wed, 13 Jan 2010 20:41:54 GMT

     [ https://issues.apache.org/jira/browse/AVRO-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aaron Kimball updated AVRO-314:
-------------------------------

    Attachment: AVRO-314.2.patch

Doug,

This mirrors the framework already in use via HADOOP-5107. Hadoop already has an established
resolver set which will read from local a mvn repository; no further modifications to those
three projects are required if we integrate with their toolchain on this end. This is, for
example, the accepted way to test how changes made to hadoop-core affect the mapreduce project.
 In any case, I think this is superior to manually copying build artifacts to specific directories.

As for your other comments -- all good suggestions. I had missed the auto-generated pom. I've
removed the static pom file, and cleaned up the other things you mentioned.

> Allow Avro to publish to a local m2 repository
> ----------------------------------------------
>
>                 Key: AVRO-314
>                 URL: https://issues.apache.org/jira/browse/AVRO-314
>             Project: Avro
>          Issue Type: Improvement
>          Components: build, java
>            Reporter: Aaron Kimball
>         Attachments: AVRO-314.2.patch, AVRO-314.patch
>
>
> To test Hadoop or other systems with a locally-built avro jar, it is considerably easier
if you can use a local maven repository to resolve 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