> bcel/bcel/5.1 and ant-contrib/ant-contrib/1.0b3. Both of these poms are > structurally incorrect:
bcel moved to o.a.bcel and has a 5.2 release with a proper pom file: http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/bcel/bcel/5.2/bcel-5.2.pom ant-contrib 1.03b does look to be wrong, you should ping that team/list to ask them to push a new build (1.03b is from Jan 2009) that has, among other things, a proper pom file (and hopefully a more sensible version number) > original question remains - is this maven behavior intended and, if so, can > we increase the urgency of fixing bad poms in maven central (repo1.maven.org) > so I don't have to host a lot of already-available artifacts just to fix > their metadata? Fixing bad metadata is generally the responsibility of the dev team who is producing the artifacts. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
