Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-project release doesn't work properly with sibling dependencies #181

Open
swpalmer opened this issue Jul 6, 2016 · 1 comment
Open

Comments

@swpalmer
Copy link

swpalmer commented Jul 6, 2016

Consider a multi-project scenario with:
ParentProject
Project_A
Project_B

Where Project_A depends on Project_B using:
dependencies {
some_config project(':Project_B')
}

A release is done from ParentProject

What is desired is that all the sub-projects are released and the release builds of each are used as the dependencies for sibling projects. However the 'unSnapshotVersion' task is not executed on the dependencies (e.g. Project_B) before they are built enough to satisfy the dependencies of sibling projecst (Project_A).
So in the above case Project_A will be released with a build of Project_B that still indicates it is a snapshot.

@amaslak
Copy link

amaslak commented May 12, 2017

Try this one
#180 (comment)

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

No branches or pull requests

2 participants