Skip to content
This repository has been 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

Open
maheshkelkar opened this issue Jul 19, 2018 · 0 comments

Comments

@maheshkelkar
Copy link

maheshkelkar commented Jul 19, 2018

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant