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...@codehaus.org> on 2014/11/25 21:31:41 UTC

[jira] (MECLIPSE-394) Commandline Arguments do NOT override settings from pom.xml

     [ https://jira.codehaus.org/browse/MECLIPSE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MECLIPSE-394.
-----------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> Commandline Arguments do NOT override settings from pom.xml
> -----------------------------------------------------------
>
>                 Key: MECLIPSE-394
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-394
>             Project: Maven Eclipse Plugin
>          Issue Type: Bug
>    Affects Versions: 2.5
>            Reporter: Martin Höller
>
> It [was reported|http://www.nabble.com/Maven-eclipse-plugin---SNAPSHOT-2.5-and-wtp-2.0-to15845593s177.html] on the maven-users mailinglist, that specifying various command line arguments like {{-DdownloadSources=false -Declipse.wtpmanifest=true -Declipse.wtpapplicationxml=true -Dwtpversion=2.0}} has no effect. It turned out, that specifying this in the {{pom.xml}} file worked as expected. However, commandline arguments should always override settings from the pom.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)