This may be a result of pom validation checks by Artifactory itself. See: http://wiki.jfrog.org/confluence/display/RTF/Advanced - suppressing pom consistency checks. You should see a message in the server log - if you do try turning it off or deploy a fixed pom version locally.
On Wed, Sep 8, 2010 at 11:31 PM, John Singleton <[email protected]> wrote: > I have tried to use Maven 3.0 (all beta versions) on our project but the > build fails due to a metadata error in an artifact in the central > repository. The error message is: > > Error transferring file: Server returned HTTP response code: 409 for URL: > > http://blackbook.jhuapl.edu:8080/artifactory/repo/colt/colt/1.2.0/colt-1.2.0.pom- > > > [Help 1] > > Is this behavior intended? (our project builds fine with maven 2.2.1, but > I > understand that m3 does more extensive pom verification) > > If so, will there be more urgency to fixing bad data in central? The bad > colt pom is already identified in MEV-618 (05MAR09) and is still > unassigned. > > Until that happens, what is the recommended fix or workaround? > > Thanks, > John Singleton > > On Wed, Sep 8, 2010 at 9:49 AM, Brian Fox <[email protected]> wrote: > > > So if you haven't > > yet, we would like you to grab the latest 3.x build and give us your > > feedback. > > > > --Brian > > Apache Maven PMC Chair > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
