targetPath no longer relative
-----------------------------
Key: MRESOURCES-84
URL: http://jira.codehaus.org/browse/MRESOURCES-84
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: Nic Grounds
My POMs used to specify "/" as the output directory (targetPath) for resources
(i.e. <project><build><resources><resource> ... <targetPath>/</targetPath> ...)
However, with Maven 2.0.10 (i.e. maven-resources-plugin 2.3) the targetPath is
apparently not treated as relative to the build output directory.
The Maven POM reference (http://maven.apache.org/pom.html#Build) says the
default should be the base directory (and indeed not specifying a targetPath
defaults to the correct place).
However the Maven Model documentation
(http://maven.apache.org/ref/current/maven-model/maven.html#class_resource)
claims that targetPath is "relative to the target/classes directory (i.e.
${project.build.outputDirectory})"
Given a <targetPath>/</targetPath> entry I get the following:
[INFO] [resources:resources]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] Copying 39 resources to /
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] /com/blah/blah/blah/my-resource-file (No such file or directory)
--
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
