[
https://issues.apache.org/jira/browse/HDFS-9629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130063#comment-15130063
]
Vinayakumar B commented on HDFS-9629:
-------------------------------------
bq. What do you think?
Instead, How about combine this with the patch.
In current patch, year is determined from current date, instead lets take as a
property, which can be overridden if required during build.
Release manager only has to take care of changing at one place, instead of
everywhere.
1. Idea is to have a system property in root pom.xml,
{code:xml} <properties>
<release-year>2016</release-year>
</properties>{code}
2. In all html replace the footer as below.
{code}<div class="col-xs-2"><p>Hadoop, {release-year-token}.</p></div>{code}
3. And replace this token in all html files during build. (In Future, may be
some other components also might need same treatment otherwise)
{code} <replace dir="${project.build.directory}/webapps"
value="${release-year}">
<include name="**/*.html"/>
<replacetoken>{release-year-token}</replacetoken>
</replace>{code}
Just, extra step for ReleaseManager is to replace {{2016}} with year of
release, at the time of changing version from *-SNAPSHOT.
> Update the footer of Web UI to show year 2016
> ---------------------------------------------
>
> Key: HDFS-9629
> URL: https://issues.apache.org/jira/browse/HDFS-9629
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Xiao Chen
> Assignee: Xiao Chen
> Labels: supportability
> Attachments: HDFS-9629.01.patch, HDFS-9629.02.patch,
> HDFS-9629.03.patch, HDFS-9629.04.patch, HDFS-9629.05.patch, HDFS-9629.06.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
