Refactor to use packages about java-sparkpost HOT 4 CLOSED

It looks like other Java SDKs are using this library: http://hc.apache.org/httpcomponents-client-ga/

from java-sparkpost.

I think this should probably be opened as a separate issue but I thought we could discuss first.

I think the structure of the project should be re-worked. It is more common for Maven based projects to have a structure like this:

• root
• pom.xml #root pom
  • apps
    • pom.xml # apps pom
    • sample-app
      • pom.xml # this app pom
    • another-sample-app
      • pom.xml # this app pom
• libs
  • pom.xml # libs pom
  • java-sparkpost-lib
    • pom.xml # sparkpost lib pom (this is the one that goes to Maven repo)

This way the java-sparkpost-lib can be pushed to a Maven repo. The apps can be various example of how to use the lib.

Thoughts?

from java-sparkpost.

I put an example of what I am thinking in this branch: feature/issue6_libify_sdk

I also added:

• static code analyzer and fixed all the warnings
• Added Lombok

Let me know what you think.

from java-sparkpost.

@colestrode do you have some time to review @yepher 's suggestions here?

from java-sparkpost.