Remove dependency to oss-parent and copy to local pom.xml

[slachiewicz]

First - remove only parent-pom.
Next, i will add selected plugin updates from #337

cc: @khmarbaise could You help with validation?

[coveralls]

Coverage remained the same at 66.005% when pulling 8c5a3f5 on slachiewicz:feature/340 into abbce69 on asciidoctor:master.

[coveralls]

Coverage remained the same at 66.005% when pulling 8c5a3f5 on slachiewicz:feature/340 into abbce69 on asciidoctor:master.

[coveralls]

Coverage remained the same at 66.005% when pulling 3bca275 on slachiewicz:feature/340 into abbce69 on asciidoctor:master.

[abelsromero]

Looked into this and I think we can totally remove the parent. After all we are publishing through jcenter.

[slachiewicz]

Yes, we can remove parent-pom, but we should include all that was defined here.
I try to compare effective pom (mvn help:effective-pom) before, and after patch and looks equal.
Later you can remove a reduntant entries

[abelsromero]

Yes, we can remove parent-pom, but we should include all that was defined here.

I totally agree with that to be safe. But I think we can go a bit further ;)

The oss-parent maven-release-plugin adds the sonatype-oss-release profile which overwrites source, javadoc and gpg plugins. But those are already defined, and honestly the options the oss build sets seem to be outdated to me.

I am ok with going ahead and seeing if we can simplify later. But wdyt, do we take our change now?

[mojavelinux]

I'm completely in support of this change. There was a time when that parent made sense. That time has passed. So this is really just residue from an old setup.

[slachiewicz]

Ok, i've removed redundant sonatype-oss-release profile and snapshot repository.
It was good for me to check how deployment to jcenter works - thx :)
After squash - I think all should be ready now for merge.