[ 
https://issues.apache.org/jira/browse/MNG-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet updated MNG-7255:
---------------------------------
    Description: 
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.


  was:
Maven 4 plans to make the setting the version of a dependency optional using 
the version of the project version of the current module as a default value.

How about applying the same mechanism to the groupId of dependencies - if 
omitted, then the projectId of the current module (or if omitted in the module, 
then of the parent) could be used.


> Default value for groupId in dependencies
> -----------------------------------------
>
>                 Key: MNG-7255
>                 URL: https://issues.apache.org/jira/browse/MNG-7255
>             Project: Maven
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Richard Eckart de Castilho
>            Assignee: Guillaume Nodet
>            Priority: Major
>             Fix For: 4.0.0-beta-5
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to