Re: Scratching my head over repositories ...

Oh damn it! I should have figured that out! It now works. Thanks Anders! /Tommy   Från: Anders Hammar Svara: Maven Users List Datum: 24 april 2021 at 19:43:58 Till: Maven Users List Ämne:  Re: Scratching my head over repositories ... Ok, the problem is that you've declared a repositor

Re: Scratching my head over repositories ...

aven/se/natusoft/tools/codelicmgr/CodeLicenseManager/2.2.2/CodeLicenseManager-2.2.2.pom.sha1 > > And yes, the rest of the artifacts are there too. > > /Tommy > > > Från: Tommy Svensson > Svara: Maven Users List > Datum: 24 april 2021 at 15:21:03 > Till: Maven Users Li

Re: Scratching my head over repositories ...

too. /Tommy Från: Tommy Svensson Svara: Maven Users List Datum: 24 april 2021 at 15:21:03 Till: Maven Users List Ämne:  Re: Scratching my head over repositories ... I am using latest IDEA which supplies maven 3.6.3. No version ranges. My interpretation of  https://maven.apache.org/gui

Re: Scratching my head over repositories ...

ven Users List Datum: 22 april 2021 at 20:37:20 Till: Maven Users List Ämne:  Re: Scratching my head over repositories ... But it should work. At least as long as you specify the version. This is what we do when we create patched versions of external libraries. We publish them to our internal r

Re: Scratching my head over repositories ...

On 2021-04-22T18:38:24 +0200 Tamás Cservenák wrote: > > 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. Publish your PGP key. Then, add this: https://github.com/io7m/pr

Re: Scratching my head over repositories ...

But it should work. At least as long as you specify the version. This is what we do when we create patched versions of external libraries. We publish them to our internal repo but with the "correct" groupId and artifactId, but a version that identifies it as patched (1.2-ISSUE123 e.g.). I admit it'

Re: Scratching my head over repositories ...

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

Re: Scratching my head over repositories ...

I think you should be able to define your repo to take precedence over Maven Central. >From documentation Remote repository URLs are queried in the following order for artifacts until one returns a valid resu

Scratching my head over repositories ...

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 package