You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Steve Holmes (JIRA)" <ji...@codehaus.org> on 2009/04/03 00:18:12 UTC
[jira] Commented: (MNG-4123) still can't override properties in
pom.xml with -D command line settings. regression?
[ http://jira.codehaus.org/browse/MNG-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171851#action_171851 ]
Steve Holmes commented on MNG-4123:
-----------------------------------
I copied the example POM and my output shows:
<properties>
<test.include.pattern>*.txt</test.include.pattern>
<test.property>default</test.property>
</properties>
Shouldn't the test.property show "cli"?
-Steve
> still can't override properties in pom.xml with -D command line settings. regression?
> -------------------------------------------------------------------------------------
>
> Key: MNG-4123
> URL: http://jira.codehaus.org/browse/MNG-4123
> Project: Maven 2
> Issue Type: Bug
> Components: Command Line
> Affects Versions: 3.0-alpha-2
> Environment: windows vista
> Reporter: chris bedford
> Assignee: Benjamin Bentmann
> Attachments: MNG-4123.zip
>
>
> Hello...
> The original bug ( http://jira.codehaus.org/browse/MNG-1992
> ) was marked as fixed in 2.1.0, and 3.0-alpha-1
> I used a slightliy modifed version of the test case described in http://jira.codehaus.org/browse/MNG-3417
> to understand what I thought i was seeing...
> It still seems not to work as described in the original bug.
> I tried two things...
> 1) tried resource filtering (running > mvn -Dtest.property='overridden' clean verify < and catting test.xt as described in the original bug report.
> same result.
> Then I tried updating my maven resources plugin to 2.3 -- running with maven 3.0-alpha-2 (see modified pom.xml, below). Stil no luck.
> 2) next i tried
> mvn -e -Dtest.result=haha help:effective-pom
> the property setting given for test.result was still default.
> So it seems like there are two failure modes (?) . one for resource filtering, and one for interpolation process that does not involve filtering..
> or maybe they have they same root cause. In any case it seems not to work still (at least on windoze).
> thanks !
> -chris
> modified pom.xml
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <project>
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.test</groupId>
> <artifactId>test</artifactId>
> <version>1.0</version>
> <packaging>jar</packaging>
> <properties>
> <test.property>default</test.property>
> <test.include.pattern>*.txt</test.include.pattern>
> </properties>
> <profiles>
> <profile>
> <id>test.profile</id>
> <properties>
> <test.property>profile</test.property>
> <test.include.pattern>*.txt</test.include.pattern>
> </properties>
> </profile>
> </profiles>
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <artifactId>maven-resources-plugin</artifactId>
> <version>2.3</version>
> </plugin>
> </plugins>
> </pluginManagement>
> <testResources>
> <testResource>
> <directory>${basedir}/src/test/resources</directory>
> <filtering>true</filtering>
> <includes>
> <include>${test.include.pattern}</include>
> </includes>
> </testResource>
> </testResources>
> </build>
> </project>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira