You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 20, 2021. It is now read-only.
I did some more digging and it looks like making the installation location of jxbrowser configurable would solve the problem.
Context: companies using Carbon Black often specify a location on the file system where developers can install their tools (like "C:\Projects", "C:\Tools", etc.). If GFM allowed us to install the jxbrowser at such custom location it would address the problem.
I'll add an option for dynamic jxbrowser download in a next release. It will 'fix' #32 and will hopefully fix this issue as well. You can expect the new version at the end of this weekend.
Hi there and thanks for the GFM!
It looks like v0.2.0 is being flagged as a security risk by the Carbon Black corporate security software:
Version 0.1.14 worked fine, so perhaps something has changed in the way how the JXBrowser is being installed?
Best,
Jan
The text was updated successfully, but these errors were encountered: