Xml Format Maven Plugin 4.1.0

• Official split off acegi parent, this should not affect users. Please let us know if any issues are encountered with this change.

This project is going to be moving at a later date. Behind the scenes the original acegi parent is marked archived for that purpose and moved elsewhere. A new parent was put in place from github.com/hazendaz (base-parent) which is used for many maven plugins including spotbugs maven plugin. Eventually hazendaz activity will flush out a new project space for maven plugins and this one will be included. Redirection pom will be put in place when that happens. For now, the point of this release was to accomplish this split from the original parent to ensure at least for now business as usual on release process. I don't expect any more direct releases here otherwise. The site pages are still broken but fixed in the code and just not released yet. That will be fixed as soon as possible. More information will be provided at a later date in regards to movements.

Xml Format Maven Plugin 4.0.1

User Related

• Requires java 8 or better
• Requires maven 3.6.3 or better
• Added m2e to xml-check and xml-format to ignore for maven 2 integration (ie will tell m2e to do nothing)
• Confirmed working with jdk 8 through 24
• No more maven warnings due to wrong scopes used (maven 4 requirement)
• Updated all used dependencies

Build Related

• Updated to junit 5
• Cleanup of pom
• Updated all plugins and dependencies but PMD as that is waiting on parent update

note: messed up 4.0.0 release, so release is 4.0.1

Xml Format Maven Plugin 3.3.1

User Changes

• Remains java 7 compatibility / Maven 3.5.4 compatibility
• Maven artifacts now provided scope as required by maven. These are already present by using maven.
• Removed hamcrest mistakenly on source path (test library)
• Minor code cleanup
• Correct issue #36
• Adjust trimming logic to retain \n when needed
• Restructure tokenization logic

Build

• Add empty relativePath
• Add java 17 and 21 to GHA and remove java 18
• Do not run deploy GHA on forks
• Correct java 11 activation and add jdk 21 activation
• Updated hamcrest usage / junit usage
• Add enforcer plugin to ensure our binary compatibility
• Run GHA for any branch
• Added maven wrapper