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 2021/05/11 20:16:00 UTC

[jira] [Updated] (MNG-6862) Wrong command line analysis for joined profile activation

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

Michael Osipov updated MNG-6862:
--------------------------------
    Fix Version/s: 4.0.x-candidate

> Wrong command line analysis for joined profile activation
> ---------------------------------------------------------
>
>                 Key: MNG-6862
>                 URL: https://issues.apache.org/jira/browse/MNG-6862
>             Project: Maven
>          Issue Type: Improvement
>    Affects Versions: 3.6.3
>            Reporter: Karl Heinz Marbaise
>            Priority: Minor
>             Fix For: 4.0.x-candidate
>
>
> On command line you can activate profiles via {{-PprofileName}} and activating several profiles via {{-Pprofile1,profile2}}. Given the following command line:
> {{mvn -Prun-p1,-Prun-p2 ...}}
> The result is that the first profile {{run-p1}} is being activate but the second {{run-p2}} (intended profile) is *not* because those two profiles have been accidentally joined via {{,}} without giving spaces between.
>  
> The issue here is of course the {{,}} between them (without spaces) which is obviously wrong but the preceding hyphen for the second profile {{-Prun-p2}} violates the naming rules for profiles (If I correctly remember).
> From my point of view it would be good to identify such case and fail with an error...
> In the end is it a question of naming a profile? Which means is it allowed having a profile which starts with a hyphen?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)