andrzejj0

Another (mainteinance) idea: modularise the plugin: at least a separate module for the API, etc.

Use Modello for XML report generation instead of writing reports using StringBuilder. This is less error-prone and we can easily generate the XML Schema for the reports. This also fixes...

#454 Use BoundArtifactVersion with UpdatePropertiesMojo

5

High prio PR, fixes #454 for `UpdatePropertiesMojo` Regarding #454, perhaps it should be reopened 😄

While looking at XML renderers, I've noticed that they're now rendered incorrectly. Please hold the release. I'm fixing it. ```xml 1 1 0 10 1 org.apache.maven.plugins maven-antrun-plugin 1.3 1.4 1.4...

I've started working on using Modello for XML report renderers. Still thinking whether the models generated by Modello should not become the model all renderers should use. EDIT: Apparently, not...

Flipping it-property-updates-report-002-slow

4

This exercise is about investigating the flipper mentioned in the summary. As far as I've seen, it only occurs on MacOS.

Plugin uses the reserved maven prefix "maven."

2

As noted in #454, versions-maven-plugin should not be using the `maven` property prefix. Hereby changing this to `mojohaus.versions`, as agreed there. This is a breaking change.

Migrate site to markdown?

2

Just an idea. Should we migrate the site to markdown? Easier to maintain imho, plus it's compatible with github and many tools including builtin plugin in IntelliJ https://illegalexception.schlichtherle.de/maven/2013/06/17/how-to-use-markdown-syntax-with-the-maven-site-plugin/

Alternative to #718, changing the prefix to "versions" since it's already being used for `versions.skip`.