[
https://issues.apache.org/jira/browse/MNGSITE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold updated MNGSITE-366:
------------------------------------------
Summary: Document priority of --define versus <properties> (was: Document
prioritoy of --define versus <properties>)
> Document priority 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
(v8.3.4#803005)
