You can also upgrade Artifactory to 2.3.0+ which is compatible with the new format, so you wouldn't need to specify the legacy deployment mode on the client side.
On Fri, Jan 7, 2011 at 11:28 PM, vratnagiri <[email protected]> wrote: > > Thanks Ben! That was the problem and setting maven.metadata.legacy=true > solves it. > -- > View this message in context: > http://maven.40175.n5.nabble.com/Migration-to-Maven-3-0-1-Deploy-fails-with-Error-500-only-for-top-most-maven-metadata-xml-tp3332094p3332497.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
