[
https://issues.apache.org/jira/browse/AVRO-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838596#comment-16838596
]
Sean Busbey commented on AVRO-2395:
-----------------------------------
here's a walkthrough for getting the 1.8.2 avro-tools jar:
* browse to https://search.maven.org
* type "avro-tools" in the omni-search box
* click download
* click jar
leads to :
https://search.maven.org/remotecontent?filepath=org/apache/avro/avro-tools/1.8.2/avro-tools-1.8.2.jar
another option is to ship something like a "tools" tarball that has the example
schemas used for compat testing and the avro-tools jar.
> Stop including bare jars as convenience binary for Java
> -------------------------------------------------------
>
> Key: AVRO-2395
> URL: https://issues.apache.org/jira/browse/AVRO-2395
> Project: Apache Avro
> Issue Type: Task
> Components: community, java
> Affects Versions: 1.7.7, 1.9.0, 1.8.2
> Reporter: Sean Busbey
> Priority: Major
>
> currently as a project our "convenience binary" for java is the complete set
> of jars, source jars, test jars, and javadoc jars. that means as a part of RC
> vetting someone has to check all of those individual files in addition to
> checking them in the staged nexus repo.
>
> the overwhelming majority of java users will consume our releases via maven
> central. we should either
>
> * ship nothing for java out of dist.a.o
> * ship a tarball that contains the things we currently ship
> * ship a tarball that is a laid out like a repository and includes both our
> artifacts and transitive dependencies
>
> my personal preference is for "ship nothing". The last option would have the
> most potential use IMHO, since it would allow someone to easily set up a
> local repository when they need to build against our artifacts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
