[
http://jira.codehaus.org/browse/MANTTASKS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224575#action_224575
]
Andreas Kohn commented on MANTTASKS-153:
----------------------------------------
Is it possible that this fix broke exactly the opposite behavior?
With maven-ant-tasks 2.1.0 and a ant build using this snippet the output will
be "${project.artifactId}-${project.version}" instead of "test-1.0-SNAPSHOT":
{noformat}
<project xmlns:artifact="antlib:org.apache.maven.artifact.ant" default="test">
<!-- Change version to 2.1.0 here -->
<taskdef uri="antlib:org.apache.maven.artifact.ant"
resource="org/apache/maven/artifact/ant/antlib.xml"
classpath="maven-ant-tasks-2.0.9"/>
<target name="test">
<artifact:pom id="p" file="pom.xml" />
<echo>${p.build.finalName}</echo>
</target>
</project>
{noformat}
{noformat}
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>com.example</groupId>
<artifactId>test</artifactId>
<version>1.0-SNAPSHOT</version>
</project>
{noformat}
> Properties defined in Ant are not passed to Maven
> -------------------------------------------------
>
> Key: MANTTASKS-153
> URL: http://jira.codehaus.org/browse/MANTTASKS-153
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: pom task
> Reporter: Paul Gier
> Assignee: Paul Gier
> Fix For: 2.1.0
>
>
> Properties that are available in Ant are not passed to Maven. For example if
> I define a dependency in my POM that uses a property for the version, there
> is currently no way to override this property on the command line. Any
> properties set when calling Ant via the command line or set during the Ant
> build should be available in the to the Maven project through the POM task
--
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
