I have a multi-module maven project, and my gradle project has a dependency on a maven project within the same build. The problem I have is that the Maven reactor will not provide the maven artifacts to the gradle project unless the install goal is run. This creates a problem for our feature builds, as we don't wish to install the artifacts as they would impact other builds using the same build system. Is there anyway gradle could resolve these dependent maven artifacts without requiring them to be installed in a local repository?
I have a multi-module maven project, and my gradle project has a dependency on a maven project within the same build. The problem I have is that the Maven reactor will not provide the maven artifacts to the gradle project unless the
install
goal is run. This creates a problem for our feature builds, as we don't wish to install the artifacts as they would impact other builds using the same build system. Is there anyway gradle could resolve these dependent maven artifacts without requiring them to be installed in a local repository?