Upload neo-devpack-java jar artifact to central maven repository about neo-devpack-java

[fabwa]

For now, we could host our own maven repo as for public ones we should have more documentation done. For those looking for .jar can find 2.3.0 in fork

[peterszatmary]

This issue is not just about using remote repo but also mavenizing the smart contracts. the second part your solution doesnt have. if we cannot use maven central repo right now than we can definitely use github as repo in maven style ( let maven download jar from github ).

[peterszatmary]

Hi guys

i did several necessary changes in pom.xml as prepration for uploading the jar to maven central repository. Here is the pull request

I followed instructions on official maven sites and made JIRA ticket OSSRH-38312 for us to have first neo-devpack-java in central maven repository.

After that we can make release page on Github. Change artifact version to +1 (2.3.1) and start to use SNAPSHOT postfix to separate versions that are / are not already deployed in maven repo.

[peterszatmary]

Hello,

today i made some final changes to pom.xml in
pull request 17. With this configuration i succesfully deployed first deo-devpack-java to maven repo. See please
search.maven.org , issue OSSRH-38312. From my perspective after merging mentioned pull request we can close this ticket.