The maven-changes-plugin has not been updated since 2016. it is dependent on a number of very much outdated libraries wit lots of vulnerabilities that we rather do not install on our servers when compiling or testing a new version. Furthermore, changes are not kept in a separate changes.xml file anymore, but maintained using github issue management. The changes that are displayed are outdated and will not be updated in the file itself.
Therefore, the maven-changes-plugin is taken out from the pom file and site.xml files for now.
By commenting it out, it can be brought back later when the plugin is updated and potentially linked to github issue management.
averbraeck
commented
3 weeks ago
The maven-changes-plugin has not been updated since 2016. it is dependent on a number of very much outdated libraries wit lots of vulnerabilities that we rather do not install on our servers when compiling or testing a new version. Furthermore, changes are not kept in a separate
changes.xmlfile anymore, but maintained using github issue management. The changes that are displayed are outdated and will not be updated in the file itself.Therefore, the maven-changes-plugin is taken out from the pom file and site.xml files for now.
By commenting it out, it can be brought back later when the plugin is updated and potentially linked to github issue management.