Closed AiyionPrime closed 1 year ago
So you suggest the use of this rule: https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html?
I am currently on version 3.6.3
and only got the warning you mentioned in #48 (as far as I noticed).
Yes, the enforcer plugin seems to be a well suited option. Since I built maven projects on a regular basis, it has been a while; I thought there was some more native approach like a oneliner in the pom-xml, but I can't come up with it.
Anyway, on any maven 3 version you should be able to reproduce the error as soon as you hit some diagnostic targets like mvn versions:display-plugin-updates
Which does propose the enforcer plugin as well... Give me a few minutes.
I just tried using 3.0.5 it compiles and all tests work, but the mvn:versions:[...] command does drop this:
[ERROR] Project requires an incorrect minimum version of Maven. [ERROR] Update the pom.xml to contain maven-enforcer-plugin to [ERROR] force the Maven version which is needed to build this project. [ERROR] See https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html [ERROR] Using the minimum version of Maven: 3.0.5
But this might just be my system, as I'm using maven 3.6.3 as well. I'll provide a PR for 3.0.5 for now but do still recommend the usage of 3.3.9.
The draft is done; as soon as the original question is answered, I'll update or finish it accordingly.
The Simulator does not define a minimum version of maven, which might break the build process for you in the future.
Either just set it to a fixed version for now, where I'd recommend
3.3.9
due to your use of the pluginorg.jacoco:jacoco-maven-plugin
, which could be updated to version0.8.6
.Currently you state maven
3.0.5
as prerequisite in the readme.If you'd decide on which version you'd want you'd help a lot in getting rid of those Error messages during
the build phasediagnostic targets in recent maven versions.