Skip to content
This repository was archived by the owner on Jan 25, 2021. It is now read-only.

In multi-project build, POM for a project contains original name of dependency, instead of new one #74

@maheshkelkar

Description

@maheshkelkar

Working Situation:

  • I have 2 projects in my repo (project A & project B)
  • The project A has a transient dependency on project B.
  • So when I generate POM file per following config, in POM file for package A, I see package name B as a dependency

Problem:

  • However, if I rename archivesBaseName for both as "foo" and "bar" respectively
  • In POM file for package foo, I still see package B as a dependency, instead of package bar
  • Am I missing anything in following config ?

I am setting up POM file as follows:

    repositories.mavenInstaller {
        // This generates POM.xml with proper parameters
        pom {
            project {
                packaging 'aar'
                artifactId "${project.property("archivesBaseName")}"
                description 'This is my POM config'
            }
        }
    }
}

I am using following plugins:

- `com.jfrog.bintray.gradle:gradle-bintray-plugin:1.8.3`
- `com.github.dcendents:android-maven-gradle-plugin:2.1`

android gradle build tools = 3.1.0
gradle = 4.6

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions