添加链接
link管理
链接快照平台
  • 输入网页链接,自动生成快照
  • 标签化管理网页链接
相关文章推荐
斯文的佛珠  ·  Android Studio ...·  6 小时前    · 
玩足球的馒头  ·  Settings.gradle not ...·  3 天前    · 
酷酷的羊肉串  ·  The Android Gradle ...·  4 天前    · 
另类的冲锋衣  ·  The Android Gradle ...·  4 天前    · 
腼腆的菠菜  ·  wkhtmltopdf : Forums ...·  1 周前    · 
不羁的面包  ·  File /oname usage - ...·  8 月前    · 
儒雅的红豆  ·  postgresql ...·  11 月前    · 

Our Gradle builds are broken since we upgraded from
org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:3.1 to org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:3.1.1

Versions used

  • Sonar Server: 7.9.4 (build 35981) Community edition
  • Sonar Gradle plugin: 3.1.1

    Error observed

    * What went wrong:
    A problem occurred configuring root project 'xxx'.
    > Could not resolve all artifacts for configuration ':classpath'.
       > Could not resolve org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:3.1.1.
         Required by:
             project : > org.sonarqube:org.sonarqube.gradle.plugin:3.1.1
          > Could not resolve org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:3.1.1.
             > Could not parse module metadata https://nexus/content/groups/java_repo/org/sonarsource/scanner/gradle/sonarqube-gradle-plugin/3.1.1/sonarqube-gradle-plugin-3.1.1.module
                > Use JsonReader.setLenient(true) to accept malformed JSON at line 2 column 1 path $
    

    We observed that starting from version 3.1.1 on the Maven Central , there is no more module file.


    We’re using Nexus to cache our artifacts.
    Since there is no more module file, Nexus is responding with a weird html content wich causes the metadata JSON parser to fail

    Could you explain me:

  • Why there is no more module files on the central? Is that intentional?
  • Do we need to change something in our Gradle conf to be able to upgrade from 3.1 to 3.1.1?
  •