| Help with (regexp?) file mapper | Help with (regexp?) file mapper 2005-06-27 - By peter reilly
Emmanouil Batsis wrote:
> Dominique Devienne wrote:
>
>>> From: Emmanouil Batsis [mailto:Emmanouil.Batsis@(protected)]
>>> It didn't work at first but then i remembered my machine at work runs
>>> windows; It works fine after changing the from attribute to
>>> (.+)\\(.+).xml. I think i saw something regarding the path seperator
>>> and
>>> how to make it transparent to the task so i'll look for that now. Many
>>> thanks for giving me a head start!
>>>
>>
>>
>> Yes, you've run into the ugly bit in mappers, namely the fact that the
>> file separator changes on different platforms, compounded by the fact
>> that the Windows separator is a special character in regexp.
>>
>
> ${file.separator} does not work for regexp mapper but that is a minor
> issue; the real issue, IMHO, is using mappers within other tasks.
This has to be done "by hand" in the code. Most of the tasks have been
updated to allow
the new "named" mapper elements - but some for example xslt have not
been updated yet.
> For example, the xslt/style allows a nested mapper type="regexp" but
> that does not support the handledirsep attribute. regexpmapper does,
> but that subtask is not allowed by xslt!
The mapper element does allow a nested mapper which corresponds to the
same thing.
<mapper>
<regexpmapper .../>
</mapper>
Peter
>
> Anyway, i just defined a project property to use within mappers and
> that works well.
>
> Thaniks,
>
> Manos
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@(protected)
> For additional commands, e-mail: user-help@(protected)
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@(protected)
For additional commands, e-mail: user-help@(protected)
|
|
 |
