release on maven central
Closed this issue · 27 comments
Is it possible that you will release this on Maven Central or Sonatype OSS?
This would be very useful!
We'd like to integrate the project as dependency to the pwm project and it'd be necessary that your project gets published on maven central (or some other common repository). Could you do this, please? This would help your project to get further known and extended by the open source community!
See also: pwm-project/pwm#170 (comment)
I need to sort out some legal stuff to comply with my employer policies (like many companies, my employer owns intellectual property created while at the company). They are very reasonable, so I don't foresee any real issue, except some paperwork. I'll try to get this done.
Thank you! We will wait for you and then hopefully integrate your great unidecode into pwm
Any update?
I submitted my request to my employer. I may take up to a month to receive a response from the team that takes care of this kind of requests, although usually they reply in about two weeks. I'll work on this as soon as I get a green light from them.
I received the copyright release approval from my employer. I'll try to fix this issue the next weekend.
Has this library been pushed to maven central?
No
I've made a fork and upload the jar on bintray. You can find it here: https://bintray.com/rookies/maven/junidecode.
I've also requested the inclusion in JCenter (then Maven Central) but it will take some time. In the meantime you can configure the repository and use it from there.
In order to be accepted in JCenter and Maven Central is needed to change the group id in something like org.gcardone.
Here the message I've received about:
JCenter hosts open source applications using the Maven naming convention which has 3 components. For example, a valid allocated path might be: org/apache/maven
The path of the file you have requested to include is missing one of the components.
Please update your JCenter inclusion path and we will be glad to approve the request.
With Regards,
JFrog Support
@gcardone best is that you update your package and I can upload a new version, or we just use it from an external repository, which is better than including the dependency manually ;-)
I'm oncall today. I may as well do something useful, rename the package, and figure out how Maven Central works.
@gcardone Great! Thanks!
If you get the PR #7 you will get the configuraiton for uploading to bintray (you have to create a new repository and set up your credential in your .gradle directory).
In the meantime I'm using my bintray repo but I've added all the references to your github repository: https://bintray.com/rookies/maven/junidecode.
I'm trying to get version 0.3 on maven central and come back to you if there are other changes required.
@gcardone the package has been accepted. Is it OK if I do the synchronisation from bintray to maven central this time or do you want to take care of it yourself?
Thanks for making it simpler for me lfoppiano@ :) However, I think it would be useful for me to learn how to publish the artifacts. I opened an issue with sonatype to get a repository there.
I promoted the first JUnidecode release on OSSRH. Once the sync process is active (tracked by https://issues.sonatype.org/browse/OSSRH-41762) I will update the documentation and close this issue.
Awesome, v0.4 is live!
https://search.maven.org/artifact/net.gcardone.junidecode/junidecode/0.4/jar
Thanks a lot @gcardone
Great, I'm going to remove version 0.3 it from my repository 👍
Thank you for bearing with me people :)
I'm going to update the documentation tonight/tomorrow and then close this issue.
I ran into a small issue when I tried to update my pom dependency to your latest version:
It looks like you used the gradle build file to build and deploy the new version which does not specify compiler runtime compatibility like the pom file does. The current release v0.4 seems to be built built with JDK 10 FOR Java 10 thus making it impossible to run the lib with Java 8 or anything below Java 10.
I don't see a reason for this change, can you probably specify compiler runtime compatibility in your gradle build file and publish a new version on Maven central? Thanks!
The reason for the change is that I didn't think about it, sigh.
I will fix it later today and upload a new artifact.
I pushed a new repository release, it should be live soon. I will update the documentation tomorrow.
Awesome, thanks a lot! 👏
I released v0.4.1 on Maven Central, which is exactly the same as 0.4, but built with target compatibility for 1.7. Let me know if there are any issues.
Works, thanks!
I updated the readme file. Thanks everyone!