[
https://issues.apache.org/jira/browse/HADOOP-19769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048582#comment-18048582
]
Stamatis Zampetakis commented on HADOOP-19769:
----------------------------------------------
The idea for the plugin came up while reviewing HADOOP-19763 and YARN-11913.
> New maven plugin for checking XML files for deprecated properties
> -----------------------------------------------------------------
>
> Key: HADOOP-19769
> URL: https://issues.apache.org/jira/browse/HADOOP-19769
> Project: Hadoop Common
> Issue Type: Task
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Major
>
> Some of the configuration files that exist in the project contain deprecated
> properties. Files such as
> [core-default.xml|https://github.com/apache/hadoop/blob/ee73a9b7db7db9d213354c5ffc33c3d8027c10c6/hadoop-common-project/hadoop-common/src/main/resources/core-default.xml]
> act as templates for end-users and serve as basis in every new deployment.
> Leaving deprecated properties in the templates leads to the proliferation of
> deprecations increasing technical debt.
> I propose to implement a new maven plugin that collects all deprecated
> properties present in the project (using bytecode analysis) and then checks
> that the XML configuration files (at least *default.xml) do not contain such
> entries.
> Given that the deprecation definitions are spread across modules and they
> require the class to be loaded its difficult/impossible to perform the checks
> using regular unit testing thus a custom maven plugin seems to be the
> cleanest option.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
