You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Elias Elmqvist Wulcan (JIRA)" <ji...@apache.org> on 2019/03/29 10:31:00 UTC

[jira] [Created] (MNG-6620) Document prioritoy of --define versus

Elias Elmqvist Wulcan created MNG-6620:
------------------------------------------

             Summary: Document prioritoy of --define versus <properties>
                 Key: MNG-6620
                 URL: https://issues.apache.org/jira/browse/MNG-6620
             Project: Maven
          Issue Type: Wish
            Reporter: Elias Elmqvist Wulcan


I'm pretty sure -D or --define to mvn is supposed to override properties defined in pom.xml under <properties> but I cannot find this documented anywhere.

Please document this behavior.

I imagine there might be some complexity here regarding inheritence, pom import, profiles and Java's system properties.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)