Hub uses guava Optionals pretty heavily. I found this out when I tried to write Optional.empty() and got an error. IntelliJ agrees that java native's Optional is superior and it helped me do some refactoring. There were a couple cases more complicated than replacing absent with empty (the most complicated of them was replacing asSet), but generally this was pretty trivial. IntelliJ also decided to expand a bunch of import *s.
I didn't replace everything; just until the code started compiling again without mention of guava's Optional in any of the files I touched. It's a start, though.
If folks think this is a relatively safe change to consider merging, I'll deploy it to dev and run tests there beforehand. Local integration tests were green.
Hub uses guava
Optionals pretty heavily. I found this out when I tried to writeOptional.empty()and got an error. IntelliJ agrees that java native'sOptionalis superior and it helped me do some refactoring. There were a couple cases more complicated than replacingabsentwithempty(the most complicated of them was replacingasSet), but generally this was pretty trivial. IntelliJ also decided to expand a bunch ofimport *s.I didn't replace everything; just until the code started compiling again without mention of guava's
Optionalin any of the files I touched. It's a start, though.If folks think this is a relatively safe change to consider merging, I'll deploy it to dev and run tests there beforehand. Local integration tests were green.