You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "David C. Hicks" <dh...@i-hicks.org> on 2009/07/15 23:47:56 UTC
Resource filtering is escaping backslashes.
Hi guys,
One of the fellows working on my project is suddenly having a problem
with one module. We've narrowed down the problem, but I have no idea
why it's happening. One of the resources in the "test/resources" tree
gets filtered with the ${project.build.directory}. In his case, he gets
a lot of escaped backslashes. (It's on Windows XP.) The rest of us are
all on some flavor of Unix. So, we don't see this. In this case, the
filtered value comes out as:
C\:\\workspace\\salient\\salient-persistence\\
When our functional tests attempt to use this directory to locate a
file, it fails. What I can't figure out is why these characters are
being escaped. This only started recently, but I can't isolate a change
that might have caused it.
Anyone got some wisdom that will help?
Thanks,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Resource filtering is escaping backslashes.
Posted by "David C. Hicks" <dh...@i-hicks.org>.
Thanks, Olivier. I thought this message had gotten lost in all the
static over voting for documentation. I appreciate your response.
Dave
Olivier Lamy wrote:
> Hi,
> It's a known issue [1].
> So you have to use resources plugin version 2.2.
> I have a a 2.4 release of this plugin in my TODO list (and I have
> planned to do this in the next weeks).
>
> --
> Olivier
> [1] http://jira.codehaus.org/browse/MRESOURCES-81
>
> 2009/7/15 David C. Hicks <dh...@i-hicks.org>:
>
>> Hi guys,
>>
>> One of the fellows working on my project is suddenly having a problem
>> with one module. We've narrowed down the problem, but I have no idea
>> why it's happening. One of the resources in the "test/resources" tree
>> gets filtered with the ${project.build.directory}. In his case, he gets
>> a lot of escaped backslashes. (It's on Windows XP.) The rest of us are
>> all on some flavor of Unix. So, we don't see this. In this case, the
>> filtered value comes out as:
>>
>> C\:\\workspace\\salient\\salient-persistence\\
>>
>> When our functional tests attempt to use this directory to locate a
>> file, it fails. What I can't figure out is why these characters are
>> being escaped. This only started recently, but I can't isolate a change
>> that might have caused it.
>>
>> Anyone got some wisdom that will help?
>> Thanks,
>> Dave
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Resource filtering is escaping backslashes.
Posted by Olivier Lamy <ol...@apache.org>.
Hi,
It's a known issue [1].
So you have to use resources plugin version 2.2.
I have a a 2.4 release of this plugin in my TODO list (and I have
planned to do this in the next weeks).
--
Olivier
[1] http://jira.codehaus.org/browse/MRESOURCES-81
2009/7/15 David C. Hicks <dh...@i-hicks.org>:
> Hi guys,
>
> One of the fellows working on my project is suddenly having a problem
> with one module. We've narrowed down the problem, but I have no idea
> why it's happening. One of the resources in the "test/resources" tree
> gets filtered with the ${project.build.directory}. In his case, he gets
> a lot of escaped backslashes. (It's on Windows XP.) The rest of us are
> all on some flavor of Unix. So, we don't see this. In this case, the
> filtered value comes out as:
>
> C\:\\workspace\\salient\\salient-persistence\\
>
> When our functional tests attempt to use this directory to locate a
> file, it fails. What I can't figure out is why these characters are
> being escaped. This only started recently, but I can't isolate a change
> that might have caused it.
>
> Anyone got some wisdom that will help?
> Thanks,
> Dave
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org