You have 2 options:
Either fix the POM and deploy it into a local repository (preferably
dedicated to third party libraries), where it will be found before the
corrupt POM from repo1. You can also add the POM to the excludes
pattern of the remote repo1 repository to make sure it is never
downloaded.
Or, run Artifactory with
-Dartifactory.maven.suppressPomConsistencyChecks=true to suppress this
consistency checks and have the broken POM silently installed (not
recommended, and if you choose to go this way it is best to turn the
checks back on and restart Artifactory).
HTH,
Yoav
On Jan 21, 2008 10:14 PM, TomHuybrechts <
tom.huybrechts@...> wrote:
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
Artifactory-users mailing list
Artifactory-users@...
https://lists.sourceforge.net/lists/listinfo/artifactory-users