[
https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907679#action_12907679
]
Scott Carey commented on AVRO-663:
----------------------------------
Essentially, avro-tools.jar is not for maven users. It is in the maven
repository for command line and ant/ivy users.
avro-tools.jar is simply avro.jar with most of its dependencies bundled (a
no-no in maven) and a manifest file to make 'java -jar avro-tools.jar' become a
command line tool.
So, it is a completely different packaging of avro, not an attached artifact.
Maven users that need to integrate features of the command line tool (such as
compiling .avsc and .avpr files to java classes) need a maven plugin, like that
proposed in https://issues.apache.org/jira/browse/AVRO-159. This would have
its own pom.xml and live in a directory underneath /org/apache/avro.
> avro-tools-1.4.0.jar doesn't meet the maven2 layout standard, making it
> inaccessble to maven users
> --------------------------------------------------------------------------------------------------
>
> Key: AVRO-663
> URL: https://issues.apache.org/jira/browse/AVRO-663
> Project: Avro
> Issue Type: Bug
> Components: build
> Affects Versions: 1.4.0
> Reporter: Brian Fox
>
> in /org/apache/avro/avro/1.4.0 you have avro-tools-1.4.0.jar. This should
> instead be avro-1.4.0-tools.jar (similar to sources/javadoc jar structure) if
> this is really just an attached artifact. If this is supposed to be something
> separate and avro-tools is the artifactId, then it should be in
> /org/apache/avro/avro-tools/1.4.0/avro-tools-1.4.0.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
