https://t.me/bellsoftware друзья, мы сделали канал в котором будем рассказывать о всем интересном, что происходит в OpenJDK и мире Java. Добро пожаловать!
> JFrog Artifactory, a piece of software widely used for hosting internal packages of all types, offers the possibility to mix internal and public libraries into the same “virtual” repository, greatly simplifying dependency management. However, multiple customers have stated that Artifactory uses the exact same vulnerable algorithm described above to decide between serving an internal and an external package with the same name. At the time of writing, there is no way to change this default behavior.
> JFrog is reportedly aware of the issue, but has been treating its possible fix as a “feature request” with no ETA in sight, while some of its customers have resorted to applying systemic policy changes to dependency management in order to mitigate dependency confusion in the meantime.
кратко говоря, суть в чем: если у вас есть зависимость на внутреннюю либу, но в публичном артифактори есть либа с таким же названием, но у которой выше номер версии, то вам в проект подтянется именно вторая