[
https://issues.apache.org/jira/browse/MNG-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416313#comment-17416313
]
Richard Eckart de Castilho commented on MNG-7255:
-------------------------------------------------
The feature (omitting versions from dependencies) was demoed using a recent
Maven 4 snapshot build, so I'd suppose there'd be an issue for it somewhere.
> 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
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
