[
https://issues.apache.org/jira/browse/HADOOP-10075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated HADOOP-10075:
-----------------------------------
Attachment: HADOOP-10075.010.patch
The 010 patch:
- Addresses [~raviprak]'s comment about the -2 check
- Relevant CheckStyle warnings. Also, I think it's confused about indentation
levels for lambda expressions.
- Replaces {{1024 * 64}} with a constant
- Uses constants in {{TestHttpServer}} for the types. However, for some
reason, it keeps being without a space, even though I'm directly setting the
type in the servlet with a space. Even stranger, if I directly set the type in
the servlet to a different charset (e.g. {{utf-16}}), it does keep the space.
So I'm not really sure what's going on here...
- Moved {{+}} signs as per [~templedf]'s comments
- Rebased on latest trunk
Here's the changes in github if that's easier to look at:
https://github.com/rkanter/hadoop/commit/546a7e36a7eeacf4b68fe31a1a09b9badc6b7560
I didn't remove catching {{throwable}} in {{ResourceGzMojo}}. The other Hadoop
maven plugins also do this, and I think the idea is that Maven knows how to
nicely handle a {{MojoExecutionException}} and report that properly to the user.
> Update jetty dependency to version 9
> ------------------------------------
>
> Key: HADOOP-10075
> URL: https://issues.apache.org/jira/browse/HADOOP-10075
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.2.0, 2.6.0
> Reporter: Robert Rati
> Assignee: Robert Kanter
> Priority: Critical
> Attachments: HADOOP-10075-002-wip.patch, HADOOP-10075.003.patch,
> HADOOP-10075.004.patch, HADOOP-10075.005.patch, HADOOP-10075.006.patch,
> HADOOP-10075.007.patch, HADOOP-10075.008.patch, HADOOP-10075.009.patch,
> HADOOP-10075.010.patch, HADOOP-10075.patch
>
>
> Jetty6 is no longer maintained. Update the dependency to jetty9.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
