Support for Spring DI, expire. Invert logic for getAll.

[Bessonov]

Hi Jonathan,

nice work!

Commit "Explicit @SupportALL to use getAll()" (2fb5533) fix multiple SADD's (one for each field) and break api, because I thing it's better annotate (with @SupportALL) explicit if getAll needed. I'm not angry, if you disagree (I need this for my project to save space and load :-) ).

Commit "add expire" (ff037b1) is related to issue #36.

And small commit (4c73940) to allow use JOhm with Spring dependency injection with example in README.md (581e73e).

Best Regard,

Anton

[gsharma]

Good stuff Anton! Can you please revert the code-formatting so we can examine the diff's? If you are an eclipse-user, please use this: https://github.com/gsharma/codestyles/blob/master/eclipseCodestyle.xml Thanks for also fixing issue 36. And I think an explicit SupportAll is a very good idea - your SupportAll has my support :)

[Bessonov]

Do you mean d8d4db1 (dos2unix JOhmUtils.java, BasicPer...)? There is no changes here. I've used dos2unix, because someone checked windows-style-newlines in and it looks bad (http://img26.imageshack.us/img26/8238/screenshotby.png).

But if you will, I can revert it (or better: checkout you trunk and apply others commits to keep code cleaner).

[gsharma]

That should have been me having made a change from another machine that was running windows. If you are using eclipse for an ide, after running dos2unix, you can run the eclipse code formatter: https://github.com/gsharma/codestyles/blob/master/eclipseCodestyle.xml

[Bessonov]

Done!

[asual]

Is there a chance for this patch to make it to the repository anytime soon? I'm eager to try the library in conjunction with Spring but if the project won't be maintained regularly then my only option is to start using the forked repository. The lack of official Maven artifact makes this decision even easier.

Thanks!

[gsharma]

Yes, we are planning another JOhm release. It will also include an update to Jedis v2. mvn artifact is something we had explored last year but it would require a change to the package structure, so, we backed off on doing that.