[jira] Commented: (AVRO-663) avro-tools-1.4.0.jar doesn't meet the maven2 layout standard, making it inaccessble to maven users
[ https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976905#action_12976905 ] Doug Cutting commented on AVRO-663: --- +1 this patch works for me. Thanks! > 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 >Assignee: Scott Carey > Fix For: 1.5.0 > > Attachments: AVRO-663.patch > > > 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
[ https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975931#action_12975931 ] Doug Cutting commented on AVRO-663: --- The new avro-tools-1.4.0.jar may be compliant, but I also think it's relatively useless. Folks who want to use the command-line tools need an executable jar that includes all of the dependencies. I think we should replace this with a correctly-named avro-1.4.0-tools.jar that includes dependencies. I don't think we need to worry about shading dependencies and such in this case. > 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 >Assignee: Scott Carey > Fix For: 1.5.0 > > > 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
[ https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973057#action_12973057 ] Scott Carey commented on AVRO-663: -- The new one, for 1.5.0, is maven compliant since the artifact id is 'avro-tools'. > 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 >Assignee: Scott Carey > Fix For: 1.5.0 > > > 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
[ https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972914#action_12972914 ] Brian Fox commented on AVRO-663: The content of the jar doesn't matter, the name however does if it's in a maven repo. The way it's named now, it's inaccessible via maven or maven aware tools, so why bother putting it into the maven repo? > 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 >Assignee: Scott Carey > Fix For: 1.5.0 > > > 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
[ https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972307#action_12972307 ] Scott Carey commented on AVRO-663: -- I was wrong, the current, post AVRO-647 avro-tools.jar in trunk does not contain its dependencies. Therefore, it is a standard maven jar without embedded dependencies. We can use 'fatjar', 'shade', or 'assembly' plugins to create another jar with dependencies. This should be done before 1.5.0, I'll address that in this ticket. > 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 > Fix For: 1.5.0 > > > 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
[ https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971941#action_12971941 ] Scott Carey commented on AVRO-663: -- as far as the shade-plugin there are other things it can do, like move whole dependencies around. For example, we could move paranamer into 'org.apache.avro.paranamer' and prevent jar conflicts. It can also package things into a single jar without moving them around. I haven't seen 'fatjar' before. Its worth a look. > 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
[ https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971939#action_12971939 ] Philip Zeyliger commented on AVRO-663: -- There's also "shade". http://maven.apache.org/plugins/maven-shade-plugin/. I'm not familiar with the distinctions. > 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
[ https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971937#action_12971937 ] Thiruvalluvan M. G. commented on AVRO-663: -- +1 Some projects call it fatjar. In fact there is a maven plugin for fatjar: http://code.google.com/p/maven-fatjar-plugin/ But I've not used it myself. > 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
[ https://issues.apache.org/jira/browse/AVRO-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971933#action_12971933 ] Scott Carey commented on AVRO-663: -- After AVRO-647 we now produce several separate artifacts. avro-tools.jar is still somewhat non-standard since it bundles all dependencies inside of it. Perhaps we should have avro-tools.jar only have its code, and have another jar that bundles it all together, as an attachment, e.g. avro-tools-1.5.0-withdeps.jar ? > 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
[ 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
[ 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.
[jira] Commented: (AVRO-663) avro-tools-1.4.0.jar doesn't meet the maven2 layout standard, making it inaccessble to maven users
[ 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.
