You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@usergrid.apache.org by "Alex Muramoto (JIRA)" <ji...@apache.org> on 2014/07/28 18:32:38 UTC

[jira] [Commented] (USERGRID-185) Port UG-specific components of Apigee Android SDK to UG Android SDK

    [ https://issues.apache.org/jira/browse/USERGRID-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076352#comment-14076352 ] 

Alex Muramoto commented on USERGRID-185:
----------------------------------------

Mostly complete. All non-UG code has been removed, and SDK is working. In the process of fixing some bugs that came up as a result of tearing out a few Apigee-specific methods.

> Port UG-specific components of Apigee Android SDK to UG Android SDK
> -------------------------------------------------------------------
>
>                 Key: USERGRID-185
>                 URL: https://issues.apache.org/jira/browse/USERGRID-185
>             Project: Usergrid
>          Issue Type: Story
>          Components: SDK-Android
>            Reporter: Alex Muramoto
>            Assignee: Alex Muramoto
>
> The UG Android SDK is currently in rough shape. It's missing many methods which causes the build to fail. It appears this may be due to a past attempt to port the Apigee SDK over that was not completed.
> We should start from scratch on porting the UG-specific parts of the Apigee SDK over. I've already attempted to go the other way and patch the holes in the existing UG SDK, but it's not feasible due to how much is missing.



--
This message was sent by Atlassian JIRA
(v6.2#6252)