{"action":"opened","issue":{"url":"https://api.github.com/repos/gridkit/jvm-attach/issues/3","repository_url":"https://api.github.com/repos/gridkit/jvm-attach","labels_url":"https://api.github.com/repos/gridkit/jvm-attach/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/gridkit/jvm-attach/issues/3/comments","events_url":"https://api.github.com/repos/gridkit/jvm-attach/issues/3/events","html_url":"https://github.com/gridkit/jvm-attach/issues/3","id":335757078,"node_id":"MDU6SXNzdWUzMzU3NTcwNzg=","number":3,"title":"Support custom tools.jar location","user":{"login":"cykl","id":1764725,"node_id":"MDQ6VXNlcjE3NjQ3MjU=","avatar_url":"https://avatars3.githubusercontent.com/u/1764725?v=4","gravatar_id":"","url":"https://api.github.com/users/cykl","html_url":"https://github.com/cykl","followers_url":"https://api.github.com/users/cykl/followers","following_url":"https://api.github.com/users/cykl/following{/other_user}","gists_url":"https://api.github.com/users/cykl/gists{/gist_id}","starred_url":"https://api.github.com/users/cykl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cykl/subscriptions","organizations_url":"https://api.github.com/users/cykl/orgs","repos_url":"https://api.github.com/users/cykl/repos","events_url":"https://api.github.com/users/cykl/events{/privacy}","received_events_url":"https://api.github.com/users/cykl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-26T10:33:38Z","updated_at":"2018-06-26T10:33:38Z","closed_at":null,"author_association":"NONE","body":"Hi,\r\n\r\n`jvm-attach` currently relies on a JDK being deployed as the `/../lib/tools.jar` is hard coded. Unfortunately, some organizations deploy JREs which hinder troubleshooting as many tools are not available.\r\n\r\nMy workaround is to extract `tools.jar` and `libattach.so` from the matching JDK and upload them on the server. This is lightweight, ~18MB + ~16KB,  and almost safe.  Setting `LD_LIBRARY_PATH` is easy, but the hard coded `/../lib/tools.jar` force me to store `tools.jar` in an uncomfortable path.  I would prefer to upload all that transient stuff into a safer place.\r\n\r\nWould it make sense to add a system property to set a custom path for `tools.jar`?\r\n\r\n"}}
{"actor":{"display_login":"cykl"}}