jillesvangurp
commented
5 years ago Thanks. I will upgrade to use the latest java sdk and address any compatibility issues as soon as that is released. Part of this may already have been addressed with the previous release a few weeks ago.
See https://github.com/stellar/java-stellar-sdk/pull/217 for details.
Horizon 0.18.0 Release
Horizon
0.18.0has been released, which continues additional work for a better integration with Stellar Protocol 11. This release contains breaking changes from0.17.*, including a requirement to use Postgres 9.5+, along with various changes, including deprecations, that further support the protocol changes presented in CAP-0005 and CAP-0006.You can find the official release on Github; below are the release notes.
This issue has been filed as a reminder for compatibility — if your SDK is already compatible, feel free to just respond on the thread and close it out. Thank you, and let me know if you have any questions!
Breaking changes
paging_tokenfield from/accounts/{id}endpoint./operation_fee_statsendpoint. Please use/fee_stats.Deprecations
fee_paidfield on Transaction resource has been deprecated and will be removed in 0.19.0. Two new fields have been added:max_feethat defines the maximum fee the source account is willing to pay andfee_chargedthat defines the fee that was actually paid for a transaction. See CAP-0005 for more information.manage_offerandcreate_passive_offer. The names will be changed to:manage_sell_offerandcreate_passive_sell_offerin 0.19.0.Changes
max-db-connectionsconfig parameter is set, it has a priority over the the new params. Runhorizon helpfor more information.horizon-db-max-open-connectionshorizon-db-max-idle-connectionscore-db-max-open-connectionscore-db-max-idle-connectionsfee_paidvalue in Transaction resource ( #1358 ).int64: value out of rangeerrors in trade aggregations ( #1319 ).horizon db reingestrange command.