We currently have 2 maven plugins. Below is a list of what they do, how we use them, and possible replacement/changes.

• info.magnolia:maven-bundle-plugin has 4 mojos:
  • bootstrap - used to process bootstrap files. Unused. Don't think it'll ever be, or would probably be rewritten.
  • bundle - was used to create war files ? Unused.
  • tomcat - was used to download Tomcat and package bundles. Unused.
  • download - can download and unpack any arbitrary URL but only ever used to download and untar Tomcat in the -bundle projects.
    • Could be replaced by a combination of wagon:download-single and truezip:copy (which, like its name doesn't indicate, it supposed to deal with all sorts of archive formats, including tgz)
• info.magnolia.maven.plugins:magnolia-setproperty-maven-plugin has 1 mojo which we use to set 4 properties.
  • We don't configure it, it sets the magnoliaCurrentDate, magnoliaReleaseDate, magnoliaNiceVersion and magnoliaNiceName by default
  • magnoliaCurrentDate and magnoliaReleaseDate could be set by build-helper:timestamp-property
  • magnoliaNiceName could probably be set by build-helper:regex-property - or we might let that go and enforce a correct <name> in our POMs via project health (SYS-377)
  • magnoliaNiceVersion, which is set through info.magnolia.maven.setproperty.VersionNameValueProvider could perhaps be contributed to the Mojo project, since its build-helper plugin already produces a couple of similar properties. See https://www.mojohaus.org/build-helper-maven-plugin/index.html
    • Or a relatively complex configuration of parse-version+timestamp+regex mojos. See examples for regex at https://www.mojohaus.org/build-helper-maven-plugin/usage.html