How do I resolve maven-metadata.xml conflict When replicating between 2.x to 3.x?

How do I resolve maven-metadata.xml conflict When replicating between 2.x to 3.x?

AuthorFullName__c
JFrog Support
articleNumber
000001066
ft:sourceType
Salesforce
FirstPublishedDate
2016-09-05T14:54:50Z
lastModifiedDate
2023-02-26T19:38:25Z
VersionNumber
4

The maven-metadata URL format has been changed in Artifactory 3.x; we are using a different URL format than the one we were using in version 2.x, so the destination repository will produce an error message similar to the one shown below:

 

2013-12-24 19:03:19,458 [replication-consumer-0] [ERROR] (o.a.a.r.c.l.r.LocalReplicationDeployRunnable:312) - Error while deploying item 'lib

s-release-local:org/jfrog/test/multi3:maven-metadata.xml': Conflict

 

There is no need to worry; Artifactory will generate the maven-metadata by itself based on the items pushed to it by the replication, so you can safely disregard these messages.