Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is the --filter command path absolute or relative ? #128

Closed
lionelmoi opened this issue Feb 7, 2017 · 3 comments
Closed

Is the --filter command path absolute or relative ? #128

lionelmoi opened this issue Feb 7, 2017 · 3 comments
Labels
enhancement Changes to an existing topic or feature question Inquiry that may not require changes
Milestone

Comments

@lionelmoi
Copy link
Contributor

lionelmoi commented Feb 7, 2017

I think this should be explicitly explained in the dita command arguments page.

@infotexture infotexture added enhancement Changes to an existing topic or feature question Inquiry that may not require changes labels Feb 7, 2017
@infotexture
Copy link
Member

I'll leave the original question to @jelovirt, but we should probably take this opportunity to review parameter descriptions w/r/t their support for absolute vs. relative paths and provide guidance on the preferred method(s) for specifying absolute paths for parameters like args.[ftr|hdf|hdr] that require them.

@infotexture
Copy link
Member

For related discussion, see dita-ot/dita-ot#2593.

@jelovirt
Copy link
Member

IIRC, when you pass args.filter as an Ant property, it's assumed it's an absolute file and if it happens to be relative, it's resolved against DITA-OT base directory (for backwards compatibility). If you pass --filter to CLI, relative paths are resolved against the current directory.

@infotexture infotexture added this to the 2.5 milestone May 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Changes to an existing topic or feature question Inquiry that may not require changes
Projects
None yet
Development

No branches or pull requests

3 participants