andrzejj0

I only came to this project a few weeks ago @reallyinsane. But you are indeed welcome to submit a PR if you like.

@reallyinsane let me know if you're willing to, otherwise I'll make one. Btw, aggregate support will be added as a different item -- #333

Guys, I'll look into it.

``` I get the message: [ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:2.5:update-properties (default-cli) on project aldi-bus-bom: Execution default-cli of goal org.codehaus.mojo:versions-maven-plugin:2.5:update-properties failed: Invalid segment, 1, for the 1 segment version: 'v3-rev126-1.19.1'...

I appreciate the maven versioning policy however it might fit the reality (but in such irregular cases Maven and the plugin will simply treat the whole version as qualifier), but...

The more I look into it, the more issues I see: - segment appears to be 0-based (see e.g. `AbstractVersionsUpaterMojo.determineUnchangedSegment` or `MavenVersionComparator.innerIncrementSegment`), but the comparison against the segment count suffers...

The PR will be rather large due to the fact that I'm leveraging the `InvalidSegmentException` and `InvalidVersionSpecificationException` rather than simply ignoring those; they are then handled in the Mojo itself....

> I'm getting the same error when I run `mvn versions:update-properties -DallowMajorUpdates=false -DallowMinorUpdates=false` > > but NOT if I run: `mvn versions:update-properties -DallowMajorUpdates=false` or `mvn versions:update-properties -DallowMinorUpdates=false` > > although...

Please use the newly added `-Dmaven.version.ignore` switch to filter out pre-release qualifiers. E.g. `"-Dmaven.version.ignore=.+-(M\d+|SNAPSHOT|RC.*)"` (On POSIX-compatible shells, the option must be surrounded in single or double quotes so that it's...

How about `mojohaus.versions.` for all such switches then (and then aliases for the existing ones for the time being)?