title: Gradle is failing on malformed pom.xml in Central Maven
body: <p>I have this gradle script snippet:</p>
  <pre><code>repositories {
      maven {
          url 'http://central.maven.org/maven2/'
      }
      maven {
          url 'http://repository.jspresso.org/maven2/'
      }
  }
  
  
  dependencies {
      compile 'org.codehaus.groovy:groovy-all:2.3.11'
      testCompile group: 'junit', name: 'junit', version: '4.12'
      compile gradleApi()
      compile localGroovy()
  
      // https://mvnrepository.com/artifact/xdoclet/xdoclet
      compile(group: 'xdoclet', name: 'xdoclet', version: '2.0.6') {
          exclude(group: 'generama', module: 'generama')
      }
  
      // https://mvnrepository.com/artifact/org.codehaus.generama/generama
      compile group: 'org.codehaus.generama', name: 'generama', version: '1.2.4'
  }
  </code></pre>
  <p>Now when running a build, Gradle consistently fails on downloading transitive dependencies and gives me this message:</p>
  <pre><code>&gt; Could not resolve jdom:jdom:b10.
    Required by:
        project : &gt; org.codehaus.generama:generama:1.2.4 &gt; commons-jelly:commons-jelly-tags-xml:1.1 &gt; jaxen:jaxen:1.1-beta-4
     &gt; Could not resolve jdom:jdom:b10.
        &gt; inconsistent module metadata found. Descriptor: jdom:jdom-:10 Errors: bad module name: expected='jdom' found='jdom-'
          bad version: expected='b10' found='10'
  </code></pre>
  <p>When I had a look at the content of the pom.xml file from the repository, I noticed that, although the pom.xml is in the right place, it indicates a version different than what is expected. In this case, the pom file for jdom version b10 indicates 10 instead of b10. Another issue reveals that the pom file for Commons Discovery » 20030211.213356 indicates 2d or something similar instead of version 20030211.213356. I've tried excluding the broken dependencies but only to find out that this introduces new issues of the same kind. Can you help me resolve this, please?</p>