[
https://issues.apache.org/jira/browse/HADOOP-12651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109117#comment-15109117
]
Chris Douglas commented on HADOOP-12651:
----------------------------------------
In README.md:
* ASL header?
* s/wrappers scripts/wrapper scripts/
* Unescaped underscore in HADOOP_PATCHPROCESS
* Link to Yetus?
It'd be nice if the README or each wrapper included a brief description. Usage
would come from Yetus, but someone poking around might appreciate a one-liner
that doesn't require them to invoke anything to understand what's in
dev-support.
Otherwise +1, pending jenkins. Speaking of jenkins, it won't be a problem for
trunk/future branches and branch-2 to invoke different dev-support scripts? I
assume it's diverged already, but thought I'd ask.
> Replace dev-support with wrappers to Yetus
> ------------------------------------------
>
> Key: HADOOP-12651
> URL: https://issues.apache.org/jira/browse/HADOOP-12651
> Project: Hadoop Common
> Issue Type: New Feature
> Components: scripts
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Attachments: HADOOP-12651.00.patch, HADOOP-12651.01.patch,
> HADOOP-12651.02.patch, HADOOP-12651.03.patch
>
>
> Now that Yetus has had a release, we should rip out the components that make
> it up from dev-support and replace them with wrappers. The wrappers should:
> * default to a sane version
> * allow for version overrides via an env var
> * download into patchprocess
> * execute with the given parameters
> Marking this as an incompatible change, since we should also remove the
> filename extensions and move these into a bin directory for better
> maintenance towards the future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
