line.separator property not passed properly to ant

Corporate Gadfly added a comment - 21/Nov/06 2:33 PM Here are the 2 attached files (inline for easy perusal): build.xml <?xml version= "1.0" ?> <project name= "line.separator" default = "echo" basedir= "." > <target name= "echo" description= "echo some messages" > <echo> line.separator: --${line.separator}-- os.name: --${os.name}-- </echo> </target> </project> and pom.xml <project xmlns= "http: //maven.apache.org/POM/4.0.0" xmlns:xsi= "http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation= "http: //maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd" > <modelVersion>4.0.0</modelVersion> <groupId>ca.utoronto</groupId> <artifactId>echo-app</artifactId> <packaging>pom</packaging> <version>1.0-SNAPSHOT</version> <name>Maven Echo</name> <build> <plugins> <plugin> <artifactId>maven-antrun-plugin</artifactId> <executions> <execution> <id>echo-no-properties</id> <phase>initialize</phase> <configuration> <tasks> <ant inheritRefs= " true " inheritAll= " true " > <target name= "echo" /> </ant> </tasks> </configuration> <goals> <goal>run</goal> </goals> </execution> <execution> <id>echo-with-properties</id> <phase>initialize</phase> <configuration> <tasks> <ant inheritRefs= " true " inheritAll= " true " > <target name= "echo" /> <property name= "line.separator" value= "${line.separator}" /> <property name= "os.name" value= "${os.name}" /> </ant> </tasks> </configuration> <goals> <goal>run</goal> </goals> </execution> </executions> </plugin> </plugins> </build> </project>

Basil James Whitehouse III added a comment - 06/Sep/07 2:04 PM This seems similar to my experience. I can't find any documentation or an issue that precisely captures my issue, but this entry is the closest. Adding my comment here rather than creating another issue. I started prototyping delegation to an ant script by writing the ant tasks inline with the plugins configuration. Once that worked I extracted the ant code to a separate build.xml and delegated to it using the ant task as suggested in the plugin documentation: "...it's encouraged to move all your Ant tasks to a build.xml file and just call it from the POM using Ant's <ant/> task.". Wanting to use Maven as the source of configuration I made heavy use of the Maven properties (project.build.sourceDirectory, project.build.outputDirectory, etc). The Maven property reference worked fine when I was using the inlined task but failed once it was extracted to a build.xml file. I was hoping that the Maven properties would be passed to the ant build transparently, or as long as the inhertiAll attribute was true. It surprised me that they weren't and that I'd have to essentially alias each value I needed, causing a lot of extra work. Is it possible to correct this behavior? Am I just missing something?

Basil James Whitehouse III added a comment - 06/Sep/07 2:07 PM Pardon my ignorance, I missed MANTRUN-40 and MANTRUN-64 which seem to describe my issue. (Learn to search JIRA istead of using google =)

Carlos Sanchez added a comment - 15/Jul/08 5:19 PM The need to pass all properties in covered in MANTRUN-40

Paul Gier added a comment - 01/Jul/09 3:11 PM This seems to be fixed now. Possibly as a result of MANTRUN-40