[
https://issues.apache.org/jira/browse/HADOOP-14089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164644#comment-16164644
]
Sean Busbey commented on HADOOP-14089:
--------------------------------------
the {{mvninstall}} failures are 1) maven seeing different reactor modules as
having dependencies on a previous SNAPSHOT build of a module in the reactor and
the current reactor build. and 2) the fall out of those failures causing us to
not update artifacts that then are checked for correctness.
The shellcheck failures are easy enough to fix. I'm not sure The maven install
failures are correctable, but I'll take a quick look.
> Automated checking for malformed client artifacts.
> --------------------------------------------------
>
> Key: HADOOP-14089
> URL: https://issues.apache.org/jira/browse/HADOOP-14089
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 3.0.0-alpha2
> Reporter: David Phillips
> Assignee: Sean Busbey
> Priority: Blocker
> Attachments: HADOOP-14089.2.patch, HADOOP-14089.WIP.0.patch,
> HADOOP-14089.WIP.1.patch
>
>
> The jar includes things like {{assets}}, {{okio}}, {{javax/annotation}},
> {{javax/ws}}, {{mozilla}}, etc.
> An easy way to verify this is to look at the contents of the jar:
> {code}
> jar tf hadoop-client-runtime-xxx.jar | sort | grep -v '^org/apache/hadoop'
> {code}
> For standard dependencies, such as the JSR 305 {{javax.annotation}} or JAX-RS
> {{javax.ws}}, it makes sense for those to be normal dependencies in the POM
> -- they are standard, so version conflicts shouldn't be a problem. The JSR
> 305 annotations can be {{<optional>true</optional>}} since they aren't needed
> at runtime (this is what Guava does).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
