MVNII-14 was closed as "Won't fix" The central POM is a converted from m1 POM, jPox also has a valid POM in SVN
That also shows that the m1 -> m2 pom conversion doesn't work well and produces invalid POMs. Maybe this process should be enhance to validate the converted POM before deployment, and maybe slip it if non convertible. Nico. 2008/1/30, Wendy Smoak <[EMAIL PROTECTED]>: > > On Jan 30, 2008 8:18 AM, nicolas de loof <[EMAIL PROTECTED]> wrote: > > Is there a good reason to declare jpox-repository in archiva main pom ? > > > > The jpox pom.xml is a maven1 pom, and the requested artifact is > available in > > central. > > I think it was added while we waited for jpox 1.1.9 to be uploaded [1] > and it can be removed now. > > [1] http://jira.codehaus.org/browse/MEV-566 > > -- > Wendy >
