Update pom.xml for remote publish

[srbala]

No description provided.

[rmrodrigues]

What's necessary to do on this issue?

[srbala]

Setting up scm and distributionManagement to pom.xml

[decebals]

I think that it's not so necessary to resolve this issue (it's a nice to have but it's not a must to have).
In my opinion this tiny project is like a POC (prof of concept) or a template for other relative big projects like pf4j, pf4j-update, pf4j-spring, ...
The value added by this project is little (only few lines that can be copy/paste in the target application). It's only a guide line for other developers, to demonstrate how to use pf4j in an web (legacy) application. In this condition to publish on Sonatype is somehow useless.
My two cents.