[
https://issues.apache.org/jira/browse/HBASE-21667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732946#comment-16732946
]
Peter Somogyi commented on HBASE-21667:
---------------------------------------
I can't find explicit requirement that we need to set it but most Apache
project use it (e.g. Phoenix, Accumulo, Ozzie set it, but Hadoop for instance
does not).
The main benefit is parent pom sets <distributionManagement> [1] and defines
'apache-release' profile that we rely on for publishing releases.
So basically the advantage is we don't need to have the profile defined in our
main pom.xml.
[1] [https://www.apache.org/dev/publishing-maven-artifacts.html#adjust-maven]
[~busbey]: Do you know if parent pom is required by ASF policies?
> Move to latest ASF Parent POM
> -----------------------------
>
> Key: HBASE-21667
> URL: https://issues.apache.org/jira/browse/HBASE-21667
> Project: HBase
> Issue Type: Improvement
> Reporter: Peter Somogyi
> Assignee: Peter Somogyi
> Priority: Minor
> Fix For: 3.0.0, 2.2.0
>
>
> Currently HBase depends on version 18 which was released on 2016-05-18.
> Version 21 was released in August 2018.
> Relevant dependency upgrades
>
> ||Name||Currently used version||New version||Notes||
> |surefire.version|2.21.0|2.22.0| |
> |maven-compiler-plugin|3.6.1|3.7| |
> |maven-dependency-plugin|3.0.1|3.1.1| |
> |maven-jar-plugin|3.0.0|3.0.2| |
> |maven-javadoc-plugin|3.0.0|3.0.1| |
> |maven-resources-plugin|2.7|3.1.0| |
> |maven-site-plugin|3.4|3.7.1|Currently not relying on ASF version. See:
> HBASE-18333|
> |maven-source-plugin|3.0.0|3.0.1| |
> |maven-shade-plugin|3.0.0|3.1.1|Newly added to ASF pom|
> |maven-clean-plugin|3.0.0|3.1.0| |
> |maven-project-info-reports-plugin |2.9|3.0.0| |
> Version 21 added net.nicoulaj.maven.plugins:checksum-maven-plugin which
> introduced SHA512 checksum instead of SHA1. Should verify if we can rely on
> that for releases or breaks our current processes.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
