You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Brian Fox (JIRA)" <ji...@apache.org> on 2010/09/09 16:14:34 UTC
[jira] Created: (AVRO-663) avro-tools-1.4.0.jar doesn't meet the
maven2 layout standard, making it inaccessble to maven users
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.
[jira] Commented: (AVRO-663) avro-tools-1.4.0.jar doesn't meet the
maven2 layout standard, making it inaccessble to maven users
Posted by "Scott Carey (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (AVRO-663) avro-tools-1.4.0.jar doesn't meet the
maven2 layout standard, making it inaccessble to maven users
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907634#action_12907634 ]
Brian Fox commented on AVRO-663:
--------------------------------
note: i can help move these around if needed, but I need to know the intent of these jars, and then your build needs to be updated to account for future releases.
> 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.
[jira] Commented: (AVRO-663) avro-tools-1.4.0.jar doesn't meet the
maven2 layout standard, making it inaccessble to maven users
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907668#action_12907668 ]
Doug Cutting commented on AVRO-663:
-----------------------------------
The tools jar is a standalone command-line executable that bundles avro and its dependencies.
Also, FYI, AVRO-647 discusses breaking Avro into more artifacts.
> 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.