Deploy to public repo

[stil4m]

Currently this library is available on my GitHub hosted maven repository. It is ok. But far from ideally and requires users to add repository to their build file.

It would be nice to push to a public maven repo. I have no experience with this, so I will have to look into this. Any suggestions, tips or other comments are welcome.

[tubbynl]

i think this article is a sensible starting point:
https://blog.idrsolutions.com/2015/06/how-to-upload-your-java-artifact-to-maven-central/

apart from the jira ticket and the GPG signing it looks similar to publishing into a private repo

[stil4m]

Just requested the groupId.

https://issues.sonatype.org/browse/OSSRH-25865

Due to conventions the groupId of the artifact will have to change to com.github.stil4m, but I think this will be a good improvement.

[tubbynl]

cool, the last time i renamed packages you need to be carefull git recognizes the file renames correctly.

Sometimes if you rename everything at once the content of the files change too much and the it becomes a delete-add change per file

[tubbynl]

the failed build looks like the same issue on my pull-request build; if you retrigger the build it will probably be ok :s

[PG2000]

@stil4m Any news on that.
Maybe i can help you with that ?