Closed samlindsaylevine closed 1 year ago
I wanted to thank you again, Ben, for your continued work in this repository; I appreciate this functionality being available to a few of my personal projects.
I just cloned the project and issues 12, 13 still apear in the code, Do I need some other branch, then master?
I just cloned the project and issues 12, 13 still apear in the code, Do I need some other branch, then master?
This pull request was just opened yesterday and has not been merged. It is a pull request from the chrome_and_maven_fixes
branch of my fork of the repository, targeting the master
branch of this repository. Since the pull request is still open and has not been merged, my commit does not yet appear in this repository at all; only in my fork.
If you would like to, you are more than welcome to clone my fork, check out the appropriate branch, and verify that the issues have been resolved by my changes.
Thanks! Sorry for being slow on the merge...
No need to apologize and thank you again!
Fixes to build process and to ChromeBrowser for current Windows versions of Chrome.
Updated Maven "fat" target to "jar-with-dependencies". Updated Maven source/target JDK version to 1.9. Updated ChromeBrowser to look for files ending in "Cookies" in any subdirectory, to handle modern Windows Chrome that puts it in Default/Network. Updated ChromeBrowser to skip un-decryptable cookies in Windows, rather than fail with an exception, to match Mac and Linux behavior.
This PR addresses and should resolve issue #12 and issue #13 .
I have successfully rebuilt the fat JAR and updated the file that is checked into the root of the repository with the output from
/CookieMonster/target/CookieMonster-jar-with-dependencies.jar
, and also verified thatnew ChromeBrowser().getCookies()
returns the expected, non-empty result with my latest version of Chrome on Windows.