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!

2 comments
Comment actions Permalink

You could try recent IDEA 14.1 eap, just set the Maven you wish to use in “Maven home directory” option

0
Comment actions Permalink

Sounds like a blessing in disguise to me ;)   You really don't want to use Maven ranges.  No really, you don't.

0

Please sign in to leave a comment.