process-resources silently treats absolute targetPath as relative

[seanf]

It is true that the element targetPath inside resource or testResource is documented as being a relative path, but the standard maven-resources-plugin actually allows absolute paths here. The takari plugin seems to treat any targetPath as relative, which matches the documentation but not the behaviour of maven-resource-plugin.

So with this resource definition:

<resource>
  <targetPath>${project.build.outputDirectory}/data/</targetPath>
</resource>

if the project dir is /home/user/src/project/, the resource files will be written to /home/user/src/project/target/classes/home/user/src/project/target/data/ whereas the maven-resources-plugin would write them to /home/user/src/project/target/data.