This message was deleted.

Thanks for the response, but my question wasn’t about configurations but projects. We have dozens of java projects which uses gradle. If a change is made to a common library, we often need to regenerate the lockfiles for each project.. Right now I’m looping with a bash script. I was hoping there was some way to do this all from a single gradle call instead of having to call it for each project.

I don't think so, gradle does not work beyond the scope of a project as far as I'm aware. Technically you could set up a composite build to aggregate all of your projects, but this does not do well when it comes to dependency locking, as it will align all of the project's dependencies, which is not necessarily what you would want.

the composite build solution was something i was hoping for, but i get that it would force all versions to be aligned. thanks for the feedback