Hi,
On 04.10.21 12:46, mar...@aldrin.net wrote:
I did a rename of another build job. I changed the version postfix from
BLACK to SNAPSHOT, and then the same issues started to happen for
regular dependencies. This is something we have had for years working
with the name BLACK, and suddenly when
Hi again,
I tried to reproduce the fault with more logs, but I'm not able to do that.
So I guess the problem is related to when I try to uplift the parent in many
project at the same time.
So it might be that the .m2 get corrupt for the snapshot version, but I have
never seen the same issue
I did a rename of another build job. I changed the version postfix from BLACK
to SNAPSHOT, and then the same issues started to happen for regular
dependencies. This is something we have had for years working with the name
BLACK, and suddenly when I renamed it to SNAPSHOT. During that change I
can you please share the xxx part of your pom.xml,
please?
and look at logs of "mvn -X", to see precisely what urls are fetched?
Regards,
Hervé
Le samedi 2 octobre 2021, 10:58:14 CEST Martin Aldrin a écrit :
> Hi, thanks for the anser.
>
> 1. We have used this format for years in our CI. And
Hi, thanks for the anser.
1. We have used this format for years in our CI. And it works perfect for all
other dependencies.
2. Yes, the artifact exist on our nexus server. And it works perfect if I first
fetch it to my local repository.
Regards
/Martin
> On 2 Oct 2021, at 09:53, Hervé
Hervé BOUTEMY wrote:
> Looking at the log, I see "Could not find artifact com.x.commonlibrary:cl-
> parent:pom:1.5.39-20210922124845805-SNAPSHOT"
>
> It seems you referenced parent POM as "1.5.39-20210922124845805-SNAPSHOT"
> when:
> 1. you should not add the "-SNAPSHOT" suffix but
Hi Martin,
I'm replying to users@maven.apache.org because iss...@maven.apache.org is not
a mailing list where anybody answers :)
Looking at the log, I see "Could not find artifact com.x.commonlibrary:cl-
parent:pom:1.5.39-20210922124845805-SNAPSHOT"
It seems you referenced parent POM as
