adjusted pom for new package name and better scoping of dependencies

[hyandell]

Happened to notice this, thought I'd offer feedback.

Not sure if there's much value moving the versions into properties. If you had a multiproject with a parent pom, then it's a useful way to stay on the same version across the submodules, but with just the one pom file it seems to introduce the pain of having to look in two places for the relevant information to a dependency.

[danielneu]

Kind of agree, although I in this case would additionally go for depencyManagement.

The advantage I see here is, if you have two dependencies that rely on the same version, like powermock. If you don't like it, feel free to change it.

But my main goal of this change was to:

• do not package testing dependencies with the final jar
• have a better name of the solution (feel free to adjust it)
• have the correct version of the SDK in the pom