Howdy Tommy, I think you are on a thin ice with this setup: if your artifacts are in Central, why not publish them in future as well?
Having your "own" repo, while it seems cool at first glance, is usually NOT what you want, unless you can guarantee reliability, availability and speed of that of Central (or let's say 1/3 of it). Moreover, bringing your own repo with overlapping GAVs to Central is a big mistake, you are booby-trapping your users: they will always struggle just like you now, and it just complicate their bootstrap and development setup. So, IMO, bite the bullet, and continue publishing to Central. Yes, is a process, is slow and has many problems, but is still the best way to go. At least for your users. HTH, T On Thu, Apr 22, 2021 at 6:24 PM Tommy Svensson <[email protected]> wrote: > Hello fellow maven fans, > > A very long time ago I released a package to maven central. That was such > a pain that when Bintray came I switched to Bintray (the best and simplest > service I've ever used! Really sad to see it gone). Now that Bintray is no > more I realized that I can publish my packages on my own web server and > point it out as a repository in pom. So far so good. > > I'm now having a problem building a maven project using one of my own > tools: CodeLicenseManager. I'm using version 2.2.1 which is available in my > web server repository. But maven still fails to find this dependency. It > finds the others in the same repo without any problem, but not this. > > I have come to the realisation that this is because CodeLicenceManager > also exists in maven central, but latest version there is 2.1.1 and I'm > asking for 2.2.1. But since maven is finding CodeLincenseManager in maven > central, it is not looking at other repos for this version. > > So now my question is: Is there a way to force maven to look in all repos > when version is not available but artifact is ? Or is the only way out of > this to change the name or group of the artifact ? > > Best Regards, > Tommy Svensson > >
