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] [Moved] (MNGSITE-366) Document prioritoy of --define versus <properties>
Date Fri, 29 Mar 2019 12:25:00 GMT

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

Michael Osipov moved MNG-6620 to MNGSITE-366:
---------------------------------------------

    Issue Type: Improvement  (was: Wish)
           Key: MNGSITE-366  (was: MNG-6620)
       Project: Maven Project Web Site  (was: Maven)

> Document prioritoy of --define versus <properties>
> --------------------------------------------------
>
>                 Key: MNGSITE-366
>                 URL: https://issues.apache.org/jira/browse/MNGSITE-366
>             Project: Maven Project Web Site
>          Issue Type: Improvement
>            Reporter: Elias Elmqvist Wulcan
>            Priority: Major
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> 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)

Mime
View raw message