You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2018/05/11 15:25:00 UTC
[jira] [Updated] (MNG-6410) When a reactor build fails on an
artifactId which is not unique, Maven should provide the groupId when
suggesting where build should restart from
[ https://issues.apache.org/jira/browse/MNG-6410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hervé Boutemy updated MNG-6410:
-------------------------------
Summary: When a reactor build fails on an artifactId which is not unique, Maven should provide the groupId when suggesting where build should restart from (was: When a reactor build fails on an artifactId which is not unique, Maven should provide the groupId when suggesting from where build should restart from)
> When a reactor build fails on an artifactId which is not unique, Maven should provide the groupId when suggesting where build should restart from
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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
> Priority: Minor
>
> 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)