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

Allow gemPath to be specified when using custom classloader #258

Closed
mojavelinux opened this issue Dec 27, 2014 · 2 comments
Closed

Allow gemPath to be specified when using custom classloader #258

mojavelinux opened this issue Dec 27, 2014 · 2 comments
Milestone

Comments

@mojavelinux
Copy link
Member

It's not currently possible to specify both the gemPath and a custom classloader. We are missing this permutation in the list of create methods.

Additionally, I think the gemPath should be set to null by default when a custom classloader is specified. Passing a custom classloader is a strong signal that AsciidoctorJ is being run in a modular environment which should be completely isolated. We don't want to leak the global GEM_PATH (or GEM_HOME) when running in such an environment.

It is useful to be able to specify the gemPath for debugging purposes, so I still think we should have it as an option. Just not the default.

Here's the method in question: https://github.com/asciidoctor/asciidoctorj/blob/master/asciidoctorj-core/src/main/java/org/asciidoctor/Asciidoctor.java#L708-L710

@mojavelinux mojavelinux added this to the v1.5.2.1 milestone Dec 27, 2014
@mojavelinux
Copy link
Member Author

Note that this is needed for the Asciidoctor sbt plugin.

@lordofthejars
Copy link
Member

I will implement this afternoon so 1.5.2.1 release will contain as well.
El dg., 28 de des., 2014 a les 0.53 Dan Allen [email protected] va
escriure:

Note that this is needed for the Asciidoctor sbt plugin.


Reply to this email directly or view it on GitHub
#258 (comment)
.

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

No branches or pull requests

2 participants