So that's one vote for antRun for a the totally common need to copy files.
I am also suspecting that <resources> behavior depends on the
<packaging> type although I haven't tested that theory and this doesn't
seem to be documented anywhere.
On 6/20/2007 4:33 PM, Wendy Smoak wrote:
On 6/20/07, Paul Copeland <[EMAIL PROTECTED]> wrote:
Trying to use <build><resources> to copy resource files to an arbitrary
target directory. The problem is that the resource phase insists on
copying to target/classes no matter what I have for targetPath.
Maven isn't really into "arbitrary". :) I assume it means 'target
path inside the jar', which is why it's going to target/classes.
This is the latest attempt - unfortunately it tried to copy to
target/classes/targetResources. Even if I add ${basedir} it still tries
to copy to a subdirectory of classes. This is not what I want. Is there
a "copy file" plugin?
You can use the Antrun plugin.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
