Hello Maxime, 2010/11/17 Maxime Gréau <greaumax...@gmail.com>
> > I tested your configuration and it works fine for me (Apache Maven 3.0 > and exec-maven-plugin-1.0) > > First, you can execute : mvn help:effective-pom > You will see the real path returned by the property > ${project.build.directory}. This is the output after calling "mvn help:effective-pom install" using "${project.build.directory}" [...] <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.1</version> <executions> <execution> <id>test2</id> <phase>install</phase> <goals> <goal>exec</goal> </goals> <configuration> <executable>echo</executable> <commandlineArgs>D:\development\projects\test\target</commandlineArgs> </configuration> </execution> </executions> </plugin> [...] [INFO] --- exec-maven-plugin:1.1:exec (test2) @ test --- [INFO] D:developmentprojectstesttarget I changed my configuration and used the correct Windows-path directly: <commandlineArgs>D:\development\projects\test\target</commandlineArgs> And the output is still wrong. Next I changed "\" to "/": <commandlineArgs>D:/development/projects/test/target</commandlineArgs> And now I get the complete path: "[INFO] D:/development/projects/test/target" Looks like a bug inside the exec-maven-plugin, which filters all "\" characters. Kind regards, Lars