You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/05/18 21:43:00 UTC
[jira] [Assigned] (MNG-6410) Add groupId to --resume-from
suggestion if artifactId is not unique in reactor
[ https://issues.apache.org/jira/browse/MNG-6410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov reassigned MNG-6410:
-----------------------------------
Assignee: Michael Osipov
> Add groupId to --resume-from suggestion if artifactId is not unique in reactor
> ------------------------------------------------------------------------------
>
> Key: MNG-6410
> URL: https://issues.apache.org/jira/browse/MNG-6410
> Project: Maven
> Issue Type: Bug
> Components: Command Line
> Affects Versions: 3.5.3
> Reporter: Ćukasz Dywicki
> Assignee: Michael Osipov
> Priority: Minor
> Fix For: 3.5.4-candidate
>
>
> In multi module builds same artifact id can be repeated with different group id. For example if project strategy is to use nesting of modules, instead of using long artifact names, {{ap}} or {{model}} module can occur multiple times with different group id.
> By default maven, upon failed build, prints out only {{-rf :artifactId}}. When developer will copy given suggestion and run build again then his build will be started from first module which have given artifact id.
> While severity of this bug is quite low, it affects productivity in bigger projects big time. To improve usability of returned message a Maven should return {{-rf groupId:artifactId}} once artifact id is not unique.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)