> But I end up with a path that is a concatenation of ${maven.test.dest}
> and ${maven.build.dest}. So, it looks like the targetPath element does
> not handle absolute references properly. In this case, it's not a
> problem, since I can put applicationContext.xml in ${maven.test.dest}
> just the same as putting it in ${maven.build.dest}.
>
No, the targetPath is defined as being relative to maven.build.dest
(for normal resources) and maven.test.dest (for unit test resources).
You shouldn't put your test resources in maven.build.dest as they'll
end up in the JAR (or whatever is being built).
> I'm just wondering if there are plans to check for absolute references
> vs relative references within these tags. If not, why set these
> property values as absolute references instead of relative?
No, there is not. Sorry I didn't understand the last sentence here...
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
