avro-dev mailing list archives

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

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

Doug Cutting updated AVRO-314:

    Fix Version/s: 1.3.0
         Assignee: Aaron Kimball
           Status: Open  (was: Patch Available)

This is really close:
 - the ant tasks don't need to explicitly depend on tasks that their dependencies already
depend on
 - we shouldn't have the maven-ant-tasks version number both in ivy.xml and build.xml -- that's
two places to update when we upgrade.
 - we shouldn't cut-and-paste the pom-creation around, but rather make it a task.

> 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
>            Assignee: Aaron Kimball
>             Fix For: 1.3.0
>         Attachments: AVRO-314.2.patch, AVRO-314.3.patch, AVRO-314.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.

View raw message