Preparing hbase-thirdparty release 4.1.3RC1; tagging and updates to CHANGES.md and RELEASENOTES.md
Signed-off-by: Duo Zhang <zhangduo@apache.org>
diff --git a/CHANGES.md b/CHANGES.md
index b6203ad..ca3a4a5 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -18,7 +18,7 @@
-->
# HBASE Changelog
-## Release thirdparty-4.1.3 - Unreleased (as of 2022-11-08)
+## Release thirdparty-4.1.3 - Unreleased (as of 2022-11-11)
@@ -41,6 +41,7 @@
| JIRA | Summary | Priority | Component |
|:---- |:---- | :--- |:---- |
| [HBASE-27467](https://issues.apache.org/jira/browse/HBASE-27467) | [hbase-thirdparty] Bump thirdparty dependencies | Major | dependencies, thirdparty |
+| [HBASE-27478](https://issues.apache.org/jira/browse/HBASE-27478) | [hbase-thirdparty] Use maven flatten plugin to generate final pom | Major | build, pom, thirdparty |
## Release thirdparty-4.1.2 - Unreleased (as of 2022-10-06)
diff --git a/RELEASENOTES.md b/RELEASENOTES.md
index a2cf57e..2211f77 100644
--- a/RELEASENOTES.md
+++ b/RELEASENOTES.md
@@ -40,6 +40,13 @@
After this change, you can not use mvn versions:set to bump the version, instead. you should just modify the parent pom to change the value of the 'revision' property in the properties section.
+---
+
+* [HBASE-27478](https://issues.apache.org/jira/browse/HBASE-27478) | *Major* | **[hbase-thirdparty] Use maven flatten plugin to generate final pom**
+
+Use flatten maven plugin to resolve all the profiles and properties in the poms which are deployed.
+
+
# HBASE thirdparty-4.1.2 Release Notes
diff --git a/pom.xml b/pom.xml
index 92f5171..1523e85 100644
--- a/pom.xml
+++ b/pom.xml
@@ -122,7 +122,7 @@
<developers />
<!--TODO-->
<properties>
- <revision>4.1.4-SNAPSHOT</revision>
+ <revision>4.1.3</revision>
<maven.javadoc.skip>true</maven.javadoc.skip>
<maven.build.timestamp.format>
yyyy-MM-dd'T'HH:mm
