Nexus maven central is a good alternative to jitpack.
I think nexus is a good alternative to the jitpack. Also, the dependency should be like that;
<dependency>
<groupId>just.domain.name</groupId>
<artifactId>Simple-Configuration</artifactId>
<version>1.7</version>
</dependency>
<dependency>
<groupId>just.domain.name</groupId>
<artifactId>Simple-Yaml</artifactId>
<version>1.7</version>
</dependency>
just.domain.name should be like for example io.github.portlek which's not including the Simple-YAML. In this case, the groupId should be me.carleslc and this will make the library more clear.
But I guess it's not allowed with the jitpack right?
JitPack is a different repository. It's pretty easy to use. Builds are automatically deployed to JitPack's repository with every commit and release. I think I cannot change the groupId they provide, though.
Publishing to Maven Central would be more trustworthy, that's a fact.
But I would need to host a Nexus instance? I've never used Nexus nor published to Maven Central.
Not actually, you can but there is a general sonatype maven central. Here is the tutorial; https://central.sonatype.org/pages/ossrh-guide.html Don't worry about sonatype's pom.xml format, I did a parent pom project for sonatype publishing. https://github.com/portlek/ppom/blob/master/pom.xml You can add parent pom on your library or you can just copy my ppom's pom.xml file to your library. Same thing.
BTW,
I can't get the jar
It can't find it.
Strange, it is working for me with com.github.Carleslc.Simple-YAML.
It's right there: https://jitpack.io/com/github/Carleslc/Simple-YAML/Simple-Configuration/1.7/
I was trying to change the groupId of JitPack, and this is also working for me:
<dependency>
<groupId>me.carleslc.Simple-YAML</groupId>
<artifactId>Simple-Configuration</artifactId>
<version>1.7</version>
</dependency>
https://jitpack.io/me/carleslc/Simple-YAML/Simple-Configuration/1.7/
I've also attached the javadoc jar to JitPack.
Any news on this?
JitPack is a different repository. It's pretty easy to use. Builds are automatically deployed to JitPack's repository with every commit and release. I think I cannot change the groupId they provide, though.
If you own a domain you can change the groupId, better said if you want me.carleslc as your groupid you would need to own the domain carleslc.me.
Read more here!
JitPack is a different repository. It's pretty easy to use. Builds are automatically deployed to JitPack's repository with every commit and release. I think I cannot change the groupId they provide, though.
If you own a domain you can change the groupId, better said if you want
me.carleslcas your groupid you would need to own the domaincarleslc.me.Read more here!
It's already possible to fetch the dependency using the me.carleslc groupId, as stated in the README.
<dependency>
<groupId>me.carleslc.Simple-YAML</groupId>
<artifactId>Simple-Yaml</artifactId>
<version>1.8.2</version>
</dependency>
Agreed, having to set up a separate repository to pull this dependency is a no-go for us due to how we proxy dependency repos. It is a shame because I would much rather explore using this than directly using snakeyaml. The API looks awesome.