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

LOADPATH and cluster.pan.includes #174

Open
wpoely86 opened this issue Oct 27, 2017 · 2 comments
Open

LOADPATH and cluster.pan.includes #174

wpoely86 opened this issue Oct 27, 2017 · 2 comments

Comments

@wpoely86
Copy link
Member

When using ant, you have pan.loadpath and cluster.pan.includes. After reading the documentation, it still not very clear to me what these two do and how they can be combined? If I understood it correctly from @stdweird, you can 'prepend' search locations of cluster.pan.includes with pan.loadpath?

It would be nice if somebody could clarify the documentation a bit.

@stdweird
Copy link
Member

stdweird commented Nov 2, 2017

@wpoely86 they are combined in the following code where the filesystem lookup of the pan templates happens:
https://github.com/quattor/pan/blob/master/panc/src/main/java/org/quattor/pan/repository/FileSystemSourceRepositoryImpl.java#L63

(and empty string is always part of loadpath)

includedirs are set outside pan, loadpath inside pan (except for the ant variable, which has no equivalent on panc commandline)

also with loadpath, you cannot break out of the includedirs.

when includedirs are not orthogonal to the loadpaths, you can expect strange issues (but they are not bugs; the behaviour is 100% predictable)

what would you like to see clarified? you want an example how it works (and how it can go wrong? 😉

@wpoely86
Copy link
Member Author

wpoely86 commented Nov 8, 2017

Some examples/guidelines how to (ab)use it would be nice.

For example, the empty string in loadpath: is it first or last or something else? I assume last?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants