I'm using RC1. Upon further research, it's not a slash issue. I
thought it was, but it's something else. I modified my variable to
convert all slashes to backslashes, and it still failed. Here's the
relevant resources section:
<resources>
<resource>
<directory>${my.meta.dir}</directory>
</resource>
</resources>
my.meta.dir is set to 'C:\mydir\mycomponent\target\myresourcedir'
If I echo out pom.build.resources, I get the following:
[[dir = C:\mydir\mycomponent]]
If, however, I change my resources to look like the following:
<resources>
<resource>
<directory>${basedir}\target\myresourcedir</directory>
</resource>
</resources>
...then I'll get the correct value for pom.build.resources:
[[dir = C:\mydir\mycomponent\target\myresourcedir]]
This seems really bizarre to me since both the values in the directory
element are technically the same (once fully resolved).
-- Sean T.
-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2003 6:11 PM
To: 'Maven Developers List'
Subject: RE: POM Build Resources and Path Problems
Never had a problem using forward slashes on windows. This sounds
unrelated.
What does your <resources/> section look like? What version of maven?
- Brett
> -----Original Message-----
> From: Sean Timm [mailto:[EMAIL PROTECTED]
> Sent: Friday, 24 October 2003 10:13 AM
> To: [EMAIL PROTECTED]
> Subject: POM Build Resources and Path Problems
>
>
> I was having some bizarre issues where the jar plugin was grabbing
> everything in my project folder as a resource, and I finally tracked
> it down to a problem with the '/' vs. the '\'
> in a directory. By default, maven.build.dir is set to something like
> the following:
> C:\mySource\currentDirectory/target. Notice how every part of the
> path has a '\' except the last part. When the jar plugin called
> maven:copy-resources, it apparently truncated off the '/target'
> portion at some point and left it at my base directory...not what I
> wanted. Up until this point, I had generally been specifying all of
> my paths with forward slashes whenever I could, but now I'm a bit
> concerned that there might be more issues like this. Is it okay for
> me to specify paths with forward slashes (and this is just a bug), or
> I should I try and avoid mixing the two up? I haven't put the issue
> in JIRA, yet...figured I'd wait until they finish (or stop) the move.
>
> Thanks!
>
> -- Sean T.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
