Richard Eckart de Castilho opened MNG-7255 and commented

Maven 4 plans already infers versions for dependencies inside the reactor, we could extend that to groupId.
Which means, that for artifacts provided by the reactor, dependencies on such artifacts may be only identified using the artifactId, provided that there's a unique matching groupId / version for such artifactId.

Issue Links:

• MNG-3863 [regression] Maven erroneously assumes "org.apache.maven.plugins" for dependencies without groupId

• MNG-8252 Fully infer the parent coordinates if the location points to a valid model

Remote Links:

• GitHub Pull Request #356
  
• GitHub Pull Request #1696
  

Backported to: 4.0.0-beta-5