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

Locking asset configuration with GCV does not work if subprojects define their own repos #1097

Open
fawind opened this issue Mar 19, 2021 · 0 comments

Comments

@fawind
Copy link
Contributor

fawind commented Mar 19, 2021

What happened?

There seems to be a bug introduced by #1012.

While writing locks for an assetBundle, sls-packaging is not respecting repository overrides defined in the bundle project. E.g. the case where we discovered this, the asset dependency gets resolved through a local maven repo that's checked in into the git repo.

A workaround is to add the repository to the root build.gradle. For example:

allprojects {
  repositories {
    maven { url project(':my-local-project').file('maven' )}\
  }
}

Internal link with more context: https://g.p.b/f/transforms-sql/pull/2181#issuecomment-1563574

cc @rshkv who flagged this.

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

1 participant