Repository navigation
Rest Authentication #475
Description
Activity
I'm having trouble building AA into a jar I can use in my project to test
it in real usage. I've tried various incantations of mvn package and mvn
install but keep getting various errors--failed tests, or unable to find
the annotations package, some sort if VerifyError (if I recall correctly)
etc. It seems to compile if I ignore the tests when I build, but using it
in the project results in no classes generated.Admittedly, I'm new to maven and am unfamiliar with this build process, but
I'm using the stable AA in another project, and got the code to generate
successfully in the test harness version of eclipse with the functional
test project. I just can't seem to get it to cooperate with my actual
project.Should I just open a pull request? I merged some changes to develop into my
branch that were made after I wrote my I initial implementation, and I'm
not positive I resolved the conflicts correctly, since I've been having
these build issues.Thanks!
On Feb 27, 2013 5:34 AM, "Pierre-Yves Ricau" notifications@github.com
wrote:Hi @dhleong https://github.com/dhleong
This looks interesting. I'm not exactly sure about what you are asking
here though. What do you need help with ?—
Reply to this email directly or view it on GitHubhttps://github.com//issues/475#issuecomment-14166908
.Well, you shouldn't create a pull request if you are not sure about what your code does and if you cannot build and test.
You should first focus on getting the thing to build and run, and know what your exact changes are.
Have you followed these steps ?
Yes, I followed those steps to get it to work in the first place, but they
don't describe how to package it. I mentioned the pull request because I
thought someone with more experience with the code base might be able to
glance at it and see something obvious that I'm messing up in the build
process.On Wed, Feb 27, 2013 at 12:03 PM, Pierre-Yves Ricau <
notifications@github.com> wrote:Well, you shouldn't create a pull request if you are not sure about what
your code does and if you cannot build and test.You should first focus on getting the thing to build and run, and know
what your exact changes are.Have you followed these stepshttps://github.com/excilys/androidannotations/wiki/InstallingEnvironment?
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/475#issuecomment-14185496
.Right. I tried that and got a bunch of errors saying
package org.androidannotations.annotations does not exist
Thanks for your help so far. I may take some time to revisit this over the weekend, perhaps pull out my code and try reintegrating it into a clean branch in case I somehow messed up one of the configuration files.
Ok :) . If you find these errors again, please post the full stacktrace.
- added a commit that references this issue
on Jul 12, 2013 Merged. I'm leave this issue open until we update the wiki
I'm using 3.0-milestone build and it looks like using @RequiresHeader for a HTTP DELETE is not adding headers.
It looks like DELETE, etc. were left out in the cold because they don't typically have an entity. I whipped up some code in my repo at home, but it's probably pretty out of date with the rest of the repo, so I'll need to take some time to pull the changes and submit a pull request. I've been pretty fried from work this past week so I haven't had a chance to get to that just yet....
If you're in a rush and can build from source, it's pretty straightforward to add in.
The two fixes have been merged. I also worked on this part of the wiki but I still have to adjust some things before updating it.
Documentation has been updated. Please let me know if you see mistakes.
Just discovered this the other day and I have to say I'm very excited by the possibilities! I thought I'd play with it for a little project I'm working on that talks to some Google APIs, but found that its authentication stuff was not as convenient as some of the others. So, I thought I'd see if I could come up with something myself. I have a fairly complete implementation (lacking some validation, I think) in a branch on my fork, but am having some difficulties figuring out how to build the jars for use in my project.
I managed to get the APIs to build and the dev Eclipse environment works to generate the code, but if I could get help building (possibly we can put together a Wiki page on it) then I can include it in my API project and do some testing, and open a pull request.
Below are my added annotations and methods.
New Annotations:
@RequiresHeader@RequiresCookie@RequiresCookieInUrl@RequiresAuthenticationsetAuthenticationorsetHttpBasicAuthconvenience method. The mix of terminology is annoying, but the relevant Spring HttpHeaders class is HttpAuthentication, sosetAuthenticationmakes more sense@SetsCookieString[]with cookie namesNew Interface methods (ala setRootUrl):
setHeader(String name, String value)RequiresHeaderannotationsetAuthentication(HttpAuthentication value)setCookie(String name, String value)RequiresCookieannotationsetHttpBasicAuth(String username, String password)RequiresAuthenticationannotationgetCookie(String name)@SetsCookie