The includeBuild in the settings script makes the bind
The included build would get it's metadata read group, module, version
and would be replaced to local file references by Gradle on the file
without repository lookup.
On 12/26/19 8:27 AM, Dr. Matthias Laux wrote:
Hi Laszlo,
then how
Hi Laszlo,
then how would the build process find the other project?
For example I have this in one of the projects:
repositories {
mavenCentral()
}
dependencies {
compile (
[group: 'org.apache.poi', name: 'poi', version: '[4.1,)'],
[group: 'org.apache.poi', name:
I do not think that storing the artifact to local maven repo is
necessary at all.
On 12/22/19 8:49 AM, Dr. Matthias Laux wrote:
Hi Laszlo,
thanks much - indeed I apparently used the wrong terminology here,
we're talking a composite build then.
However, for that syntax to work
::
I'd need
