Closed papanito closed 6 years ago
Haha ... I never thought of this as a valid use case. So essentially the process of copying artifacts from the temporary local repo on disk into the target repo uses the maven repo format naming for files and only uploads those. It does NOT use snapshot version artifacts naming. We could change this but to be allowing snapshots but to be honest that would make things more complicated as well. Because the target repo in the target server would have to have snapshot policy as well and there is no easy way to verify that.
I am inclined to NOT work on this at all. SNAPSHOT repositories are just temporary storage for development deployments. You should never really migrate them. Just point your development to the new server and new deployments go there. Old snapshots are trash anyway so you would not want to migrate them.
Please let me know if this makes sense..
Yeah you are actually right snapshot repos should not be migrated. Don't know what came over me to this morning :smile:
I try to migrate a maven2 release and snapshot repository using v.1.3.1. The migration for the release repository works fine:
Whereas the migration from snapshot repository just finish without transferring any artifact
There is no error message. Any clue what the reason for this could be?
Nexus 2: 2.14.1-01 Nexus 3: 3.13.0-01