-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Maven Version! #75
Comments
Agree.... a version release would be great. I think there are way too many breaking changes to even justify a 2.x version. What I'm currently doing is forking the repo, tagging a version 1.5.x, and using jitpack.io to publish it from my personal repo. |
thats a great Idea! I was just looking at how to fork it and do the same thing. Hey, you wouldnt happen to know is it just me or is ParseUser.getQuery() now gone. I just cloned the repo and built a jar file so I could keep working temporarily and I am getting an error even though the readme says its there. |
|
Getting a weird error that you cat cast ParseObject to ParseUser. Syntax gives me no errors. Weird. |
So I just realized a good 1/2 if not more of the documentation is copied directly from the Android library. Definitely needs to be re-written. So, thats where my confusion on the getQuery() came from. In the android version you can call ParseUser.getQuery() and it returns ParseQuery.getQuery("_User") automatically. That documentation is in the readme as well but not in this library. |
Please update maven version! At least publish this version to the central repository. I think its way due ;)! |
@thiagolocatelli joining the request for a new maven version |
I added 1.4 and it does not have the ability to initialize with a self hosted parse URL. I looked at your current pom file and tried to copy the version you have set there and maven cannot find it. Am I missing something or has this not been updated on maven yet? If so. Please update your readme.
P.S. Great library by the way. Been working on mobile/web with Parse for years. You guys did a great job following their naming conventions and everything!
The text was updated successfully, but these errors were encountered: