[oXygen-user] Feature Request: Variables for Path Components When Building Result Locations in Scenarios

[Peter West]

There is already the variable ${pdu} which is the URL of the project 
directory.  If that were complemented with ${rppd} for relative path 
within project directory, that would do the trick, wouldn't it?

On 8/02/2014 8:05 am, Eliot Kimber wrote:
....

> I'm thinking that what I'd really like is the ability to get any component
> of the input file's path so that I can then construct the result path,
> something like:
>
> ../../../newdir/${parent:3}/${parent:2}/${parent:1}/$cfn-newbit.xml
>
> Where the tokens are addressed from nearest (parent) to farthest, as for
> the ancestor:: axis.
>
> If I had that I could have single transform scenarios I could apply to
> large sets of files in different structures and get the required result
> without having to rejigger the transform scenario for each different
> output location.
>
-- 
Peter West
"For what does it profit a man if he gains the whole world and loses or 
forfeits himself?"