a long time reader, the first time asked ...
I have an autonomous network (no internet access). It has an artificial server that has virtual libs-snapshot and libs-release repositories. Libs-snapshot has 4 local snapshot repositories. The reason for this is that we get a dump of all the artificial repositories from another place (not connected) and import them into this network. But we have to change the subset of snapshot artifacts. So, we created another local snapshot repository, call it my-snapshot-local (maven 2 repo set as unique, max artifacts = 1?) And add it to the top of the virtual virtual snapshot libs-snapshot. Theoretically, this would allow us to modify a few artifacts that we need, deploy on our own repo, and local developers will pick them up.But we will still have access to 99% of the other artifacts from the periodic dump from another unrelated system. In addition, we can import drops from another network that are simultaneously changing, on a wholesale basis, without touching our offline network repo (my-snapshot-local). I think we are branching out with artificial repositories ...
I understand that we could just deploy directly to one of the imported repositories, but the next time we get a dump from another network, all these changed artifacts will disappear ... so I really would like to get this method to work if it perhaps.
from my local eclipse, the maven plugin explicitly and error-free deploys artifacts into the local my-snapshot-local repository. The problem that I see is that maven-metadata.xml for a virtual snapshot is not being updated. The timestamp of this file is updated, and if I browse the libs-snapshot / whatever_package library using a web browser, I can see my recently deployed artifacts with newer timestamps than existing snapshots. But the maven-metadata.xml file still contains pointers to the "old" snapshot.
maven-metadata.xml my-snapshot-local, , artifactory . , , -, - ( - -/pom?).
artifactory 2.6.1 ( ).
: , , , .. .
, , - , . , , , 4355. , 1 ( - , 4355).
, , ? , , , , .