maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MNG-6410) Add groupId to --resume-from suggestion if artifactId is not unique in reactor
Date Fri, 18 May 2018 21:43:00 GMT

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

Michael Osipov updated MNG-6410:
--------------------------------
    Summary: Add groupId to --resume-from suggestion if artifactId is not unique in reactor
 (was: When a reactor build fails on an artifactId which is not unique, Maven should provide
the groupId when suggesting where build should restart from)

> 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
>            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)

Mime
View raw message