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

Purpose and improvement request for the "resources/plugins.xml" [DOT 2.x] #2018

Closed
raducoravu opened this issue Aug 27, 2015 · 4 comments
Closed
Assignees
Labels
feature New feature or request priority/medium Medium (or unknown) priority issue
Milestone

Comments

@raducoravu
Copy link
Member

In DITA OT 2.x after the integrator is run there is a resource "resources/plugins.xml" which keeps a list with all the contents of all the plugin.xml's in the DITA OT distribution.
What is the purpose of that file?
Could it be modified to also include xml:base so that when I parse it and I find references like "dita.conductor.target.relative" which are relative to the plugin folder I can determine where that target is located?

@jelovirt
Copy link
Member

plugins.xml is used by e.g. documentation generation to get a list of extension points etc.

👍 for addding @xml:base to each plugin configuration element so that file paths in plugin configuration can be resolved.

@jelovirt jelovirt added feature New feature or request priority/medium Medium (or unknown) priority issue labels Aug 27, 2015
@jelovirt jelovirt added this to the 2.2 milestone Aug 27, 2015
@jelovirt jelovirt self-assigned this Aug 27, 2015
@raducoravu
Copy link
Member Author

There is a problem, the xml:base should be relative to the plugin.xml and not absolute.
In this way, I cannot share a DITA OT distribution with somebody else, commit it for example on a SVN server or in the case of Oxygen bundle it with an application.

@jelovirt
Copy link
Member

Reopening to make xml:base relative.

@raducoravu
Copy link
Member Author

Thanks Jarno, I tested and it seems to make the proper relative paths.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request priority/medium Medium (or unknown) priority issue
Projects
None yet
Development

No branches or pull requests

2 participants