[
https://issues.apache.org/jira/browse/YETUS-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey moved HADOOP-11903 to YETUS-19:
-------------------------------------------
Affects Version/s: (was: HADOOP-12111)
Component/s: (was: yetus)
Test Patch
Key: YETUS-19 (was: HADOOP-11903)
Project: Yetus (was: Hadoop Common)
> test-patch plugin for checking file name conventions
> ----------------------------------------------------
>
> Key: YETUS-19
> URL: https://issues.apache.org/jira/browse/YETUS-19
> Project: Yetus
> Issue Type: New Feature
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Kengo Seki
> Attachments: HADOOP-11903.HADOOP-12111.00.patch,
> HADOOP-11903.HADOOP-12111.01.patch, HADOOP-11903.HADOOP-12111.02.patch
>
>
> Providing yetus with the functionality to detect newly added files which
> doesn't follow the naming conventions. As for java, it also can be used for
> checking classnames. In the past, we've named things like
> DefaultResourceCalculator, DefaultContainerExecutor, and DefaultCodec that do
> nothing but cause problems down the road since they are effectively version
> and functionality locked forever. If these examples had been named what they
> truly were (e.g., MemoryResourceCalculator, SimpleContainerExecutor, and
> GZipCodec), the defaults could then be changed in the future in a compatible
> way. One way to enforce this is to prevent the creation of new classes called
> Default-anything.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
