[
https://issues.apache.org/jira/browse/MANTRUN-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Derek Lewis reopened MANTRUN-172:
---------------------------------
Retested using the zip that was attached. The bug still occurs even after
updating the maven-antrun-plugin to 1.8, the latest.
> Properties passed to Maven as -D don't get passed to <ant> invocations when a
> profile sets the same property
> ------------------------------------------------------------------------------------------------------------
>
> Key: MANTRUN-172
> URL: https://issues.apache.org/jira/browse/MANTRUN-172
> Project: Maven Antrun Plugin
> Issue Type: Bug
> Affects Versions: 1.7
> Reporter: Derek Lewis
> Attachments: maven-antrun-plugin-bug.zip
>
>
> When I invoke Maven as follows:
> mvn package -Dmy.test.property="from commandline" -Ptest-profile
> Setting my.test.property on the command line, I expect to see the following
> output from the testcase:
> [echo] pom.xml: ptest = from commandline
> [echo] pom.xml: my.test.property = from commandline
> [echo] build.xml: ptest = from commandline
> [echo] build.xml: my.test.property = from commandline
> But instead I see:
> [echo] pom.xml: ptest = from commandline
> [echo] pom.xml: my.test.property = from commandline
> [echo] build.xml: ptest = from commandline
> [echo] build.xml: my.test.property = from profile
> It looks like the <ant> task is causing properties set on the command line to
> not be inherited.
> When run without -Ptest-profile, the expected output is seen. The comments
> on MANTRUN-121 would seem to imply that properties set on the commandline
> should always be passed to sub <ant> builds, regardless of the value of the
> inheritAll property.
> I've tested with a profile in the pom as well as in settings.xml, and the
> same behavior is observed regardless of where the profile is, so long as it
> is activated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
