Remove the depecdency on signpost and commons codec.

[GoogleCodeExporter]

Removing the dependency of external jars will make the library more
reusable. Will need to implement OAuth on our own.

Original issue reported on code.google.com by nabeelmukhtar on 8 Dec 2009 at 12:00

[GoogleCodeExporter]

Re-inventing code that already exists does not seem the right way to go. The 
project
is already Mavenized. You can set up a Maven repository here:

http://nexus.sonatype.org/oss-repository-hosting.html

Exposing the snapshots and releases in a Maven repository will make it very 
re-usable
for Maven and Ivy projects.

One piece of advice though, do not use SNAPSHOT dependencies as in the case of
Signpost. They are moving targets make it harder to implement this project with 
other
code that uses Signpost.

Thank you so much for this library. I just started using it and I am loving the 
fact
that I don't have to start from scratch!

Original comment by andreas....@gmail.com on 6 Feb 2010 at 7:17

[GoogleCodeExporter]

Hi Andreas
Thanks for your feedback. The idea to get rid of signpost was driven by the 
fact that
its release version did not work with linked in. I am now trying to make the 
latest
version of signpost to work with the library. Once that's done the dependency 
on the
snapshot version will be removed and it will also be easier to enable maven
dependency management.

Thanks again.

Original comment by nabeelmukhtar on 7 Feb 2010 at 7:26

[GoogleCodeExporter]

Original comment by nabeelmukhtar on 23 Sep 2011 at 5:42

• Changed state: Fixed