EAP still uses an old Maven version internally

We really want to use Maven ranges when declaring a parent dependency but IntelliJ doesn't like this, most probably we think because of the version of Maven used internally.Everything is fine on the command line or using the Maven toolbar option, but IntelliJ doesn't like the POM if it has a range for a parent version and you can't effectively work with your project.

This is also raised at https://youtrack.jetbrains.com/issue/IDEA-129782.

Any updates would be appreciated!