[
https://issues.apache.org/jira/browse/AVRO-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799942#action_12799942
]
Doug Cutting commented on AVRO-314:
-----------------------------------
We don't have to rigidly emulate Hadoop's Ivy/Maven toolchain. Hadoop already
uses Ivy to retrieve its dependencies, so using the local Ivy repo imposes
little on Hadoop. Is there another reason why you prefer to publish to
Maven's local repo rather than Ivy's?
> In any case, I think this is superior to manually copying build artifacts to
> specific directories.
I agree. That's why I suggested we try Ivy's publish task before we resort to
using Maven.
If you're stuck on not changing Hadoop and conforming to that build, can we at
least retrieve maven-ant-tasks using Ivy as a part of our build configuration?
This should be a one-line change to Avro's ivy.xml, no?
> 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.