Gradle不包括已发布的pom.xml中的依赖项

3 回答

• 70

  通过让脚本直接使用 pom.withXml 将依赖项添加到pom，我能够解决这个问题 .

  //The publication doesn't know about our dependencies, so we have to manually add them to the pom
  pom.withXml {
      def dependenciesNode = asNode().appendNode('dependencies')
  
      //Iterate over the compile dependencies (we don't want the test ones), adding a <dependency> node for each
      configurations.compile.allDependencies.each {
          def dependencyNode = dependenciesNode.appendNode('dependency')
          dependencyNode.appendNode('groupId', it.group)
          dependencyNode.appendNode('artifactId', it.name)
          dependencyNode.appendNode('version', it.version)
      }
  }
  

  这适用于我的项目，它可能会在其他项目中产生无法预料的后果 .

  回复于 2024-04-26T03:20:29+08:00
• 26

  我升级了C.Ross解决方案 . 此示例将生成pom.xml，其中包含来自编译配置的依赖项以及特殊构建类型依赖项，例如，如果对发布或调试版本使用不同的依赖项（debugCompile和releaseCompile） . 而且它还添加了exlusions

  publishing {
      publications {
          // Create different publications for every build types (debug and release)
          android.buildTypes.all { variant ->
              // Dynamically creating publications name
              "${variant.name}Aar"(MavenPublication) {
  
                  def manifest = new XmlSlurper().parse(project.android.sourceSets.main.manifest.srcFile);
                  def libVersion = manifest['@android:versionName'].text()
                  def artifactName = project.getName()
  
                  // Artifact properties
                  groupId GROUP_ID
                  version = libVersion
                  artifactId variant.name == 'debug' ? artifactName + '-dev' : artifactName
  
                  // Tell maven to prepare the generated "*.aar" file for publishing
                  artifact("$buildDir/outputs/aar/${project.getName()}-${variant.name}.aar")
  
                  pom.withXml {
                      //Creating additional node for dependencies
                      def dependenciesNode = asNode().appendNode('dependencies')
  
                      //Defining configuration names from which dependencies will be taken (debugCompile or releaseCompile and compile)
                      def configurationNames = ["${variant.name}Compile", 'compile']
  
                      configurationNames.each { configurationName ->
                          configurations[configurationName].allDependencies.each {
                              if (it.group != null && it.name != null) {
                                  def dependencyNode = dependenciesNode.appendNode('dependency')
                                  dependencyNode.appendNode('groupId', it.group)
                                  dependencyNode.appendNode('artifactId', it.name)
                                  dependencyNode.appendNode('version', it.version)
  
                                  //If there are any exclusions in dependency
                                  if (it.excludeRules.size() > 0) {
                                      def exclusionsNode = dependencyNode.appendNode('exclusions')
                                      it.excludeRules.each { rule ->
                                          def exclusionNode = exclusionsNode.appendNode('exclusion')
                                          exclusionNode.appendNode('groupId', rule.group)
                                          exclusionNode.appendNode('artifactId', rule.module)
                                      }
                                  }
                              }
                          }
                      }
                  }
              }
          }
      }
  }
  

  回复于 2024-04-26T03:20:29+08:00
• 0

  我想这与 from components.java 指令有关，如guide所示 . 我有一个类似的设置，它的不同之处在于将该行添加到发布块中：

  publications {
      mavenJar(MavenPublication) {
          artifactId 'rest-security'
          artifact jar
          from components.java
      }
  }
  

  回复于 2024-04-26T03:20:29+08:00