Skip to content
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

Modularize Java library #41

Closed
GoogleCodeExporter opened this issue Sep 11, 2015 · 2 comments
Closed

Modularize Java library #41

GoogleCodeExporter opened this issue Sep 11, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

If somebody only wants to use the client he should not be forced to pull in
the servlet dependency.

The same thing for the commons-httpclient dependency, maybe have a generic
client and add the commons version to a separate module.

Something linke this:
OAuth-core
OAuth-client
OAuth-server
OAuth-client-httpclient

Original issue reported on code.google.com by franci...@gmail.com on 1 Oct 2008 at 4:34

@GoogleCodeExporter
Copy link
Author

You use classes from the OAuth .jar that don't depend on the commons-httpclient 
or 
servlet classes, without the latter available in your classpath.

Original comment by jmkrist...@gmail.com on 22 Oct 2008 at 5:31

  • Changed state: WontFix
  • Added labels: Lib-Java

@GoogleCodeExporter
Copy link
Author

Since I am using the oauth maven repo those other libraries are fetched
automatically, maybe those dependencies should be indicated as provided.

Original comment by franci...@gmail.com on 22 Oct 2008 at 5:52

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant