Skip to content
This repository has been archived by the owner on Dec 6, 2023. It is now read-only.

Update for API v3 #76

Merged
merged 3 commits into from
Nov 9, 2016
Merged

Update for API v3 #76

merged 3 commits into from
Nov 9, 2016

Conversation

jkutner
Copy link
Contributor

@jkutner jkutner commented Nov 4, 2016

This update is intended to convert the library to API v3, while maintaining backwards compatibility as much as possible. In the future, a 3.1.0 release will update the class structure to more accurately match what is presented in the Platform API. We also rename library, such as the ning-async to match the newer asynch-httpclient, which is actually used.

* Updated library versions
* Removed support for Play
* Added encode impl for Gson
* Removed unused deprecated code
* Refactor jersey-client to use ApacheConnectorProvider to support PATCH
* Add encode support to Json providers
* Changed app Accept headers to JSON
* Use oracle jdk8
* Revised travis test config
* Update travis keys
* Remove old keys
@@ -8,3 +8,4 @@
target
.DS_Store
*.versionsBackup
*.jkutner.profile
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could probably just go in your global gitignore.

@@ -5,7 +5,7 @@
<parent>
<artifactId>heroku-api-parent</artifactId>
<groupId>com.heroku.api</groupId>
<version>0.17-SNAPSHOT</version>
<version>3.0.0-SNAPSHOT</version>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a pretty big jump. Is 3.0 used because you want to match the API versioning?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea, 3.0 to match the API. But also because a bump to 1.0 didn't seem right. idk. i don't have a strong opinion on this. got a better suggestion? just 0.18?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have a strong opinion either, just trying to understand. At one point we didn't want to pin the heroku.jar version to the API version, but don't remember why. Also, this library technically works with both v2 and v3 of the API.

@@ -274,7 +270,7 @@ public String getHeaderName() {

@Override
public String getHeaderValue() {
return Integer.toString(version);
return "application/vnd.heroku+json; version=" + Integer.toString(version);
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While you're touching this, you might want to include the ability to set the version's variant.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Created #77

@jkutner jkutner mentioned this pull request Nov 4, 2016
@naaman
Copy link

naaman commented Nov 4, 2016

👍

@jkutner jkutner merged commit 8dbf14c into master Nov 9, 2016
@jkutner jkutner deleted the api-v3 branch November 9, 2016 14:49
@dmcinnes
Copy link

Thanks @jkutner ! Just saw this 😄

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants