fixed typo in CHANGELOG

This commit is contained in:
Massimiliano Assante 2024-05-17 10:05:34 +02:00
parent 45034760d8
commit fcf36d16ff
2 changed files with 25 additions and 22 deletions

View File

@ -1,25 +1,28 @@
<?xml version="1.0" encoding="UTF-8"?><project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="accept-invite-portlet">
<wb-resource deploy-path="/" source-path="/target/m2e-wtp/web-resources"/>
<wb-resource deploy-path="/" source-path="/src/main/webapp" tag="defaultRootSource"/>
<wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/java"/>
<wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/resources"/>
<dependent-module archiveName="invites-common-library-1.5.1.jar" deploy-path="/WEB-INF/lib" handle="module:/resource/invites-common-library/invites-common-library">
<dependency-type>uses</dependency-type>
</dependent-module>
<dependent-module archiveName="email-templates-library-1.5.0.jar" deploy-path="/WEB-INF/lib" handle="module:/resource/email-templates-library/email-templates-library">
<dependency-type>uses</dependency-type>
</dependent-module>
<property name="context-root" value="accept-invite-portlet"/>
<property name="java-output-path" value="/accept-invite-portlet/target/classes"/>
</wb-module>
<wb-module deploy-name="accept-invite-portlet">
<wb-resource deploy-path="/" source-path="/target/m2e-wtp/web-resources"/>
<wb-resource deploy-path="/" source-path="/src/main/webapp" tag="defaultRootSource"/>
<wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/java"/>
<wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/resources"/>
<property name="context-root" value="accept-invite-portlet"/>
<property name="java-output-path" value="/accept-invite-portlet/target/classes"/>
</wb-module>
</project-modules>

View File

@ -4,7 +4,7 @@
All notable changes to this project will be documented in this file.
This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [v2.1.0 - 2024-04-22
## [v2.1.0] - 2024-04-22
- Fix for Incident #27306
## [v2.0.1] - 2022-06-16