Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
all
Description
I would like to know if anybody has thought about the possibility to do some checks on the changes.xml file during a release process or before.
My ideas are as follows:
First check if a release entry does exist which contains a date of today (day of release) and a version which is relationship with the pom from where the changes-plugin is used.
Attachments
Issue Links
- duplicates
-
MCHANGES-140 Create a changes check mojo
- Closed