Update dependencies and fix some code#87
Conversation
|
Y'know, I would've preferred you specify everything you updated rather than just "I updated dependencies", but oh well I guess edit: nvm you listed everything u updated and now i look dumb |
|
I have not tested the changes. The minor dependencies updates I don't think will cause any issues, like commons-*, gson, etc. I also considered updating to the JDA-Utilities fork, Chewtilities as it supports newer features, but I figured there would be no point. My only two possible concerns would be weebJava and RethinkDB. I made sure to look at weebJava before updating and I think what I did would work. I don't see why it wouldn't work though. I also believe that RethinkDB should be fine, as the breaking update for that was 2.4.1 as far as I'm aware. Apart from that, everything should be good! |
|
I'm tempted to test the weeb commands at the very least because knowing my luck something will break. So this pull request may have to sit for a lil while until I find the time to do so |
Keepin' up with the times with up-to-date dependencies!
Updated:
jersey-bom: 2.9.1 -> 3.0.3
JUnit: 4.9 -> 4.13.2
JDA: 4.2.0_214 -> 4.3.0_339
commons-io: 2.5 -> 2.11.0
gson: 2.8.1 -> 2.8.8
commons-lang: "LATEST" -> 3.12.0 (Maven apparently doesn't like this, at least won't in the future)
Twitter4J: 4.0.6 -> 4.0.7
weebJava: 2.2.0_27 -> 3.0.1_4
RethinkDB: 2.3.3 -> 2.4.0
JDA-Utilities: 3.0.2 -> 3.0.5
logback-classic: 1.2.1 -> 1.2.6
jsoup: 1.10.1 -> 1.14.3
maven-assembly-plugin: 2.4.1 -> 3.3.0