Well, I'll be ... this is it! Thanks SO much Laszlo, you made my day :-)
Am Do., 26. Dez. 2019 um 17:54 Uhr schrieb Laszlo Kishalmi <
laszlo.kisha...@gmail.com>:
> The includeBuild in the settings script makes the bind
>
> The included build would get it's metadata read group, module, version an
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 wou
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: 'poi-oo
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
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 to store (in this case) project A in a local Maven repo since A
and B are my own stuff. I was hoping to
get it done via a filetree dir
Well this set up seems to be a bit odd.
What you described is not a multi-project build. It seems you are trying
to use two standalone Gradle projects with weak include-build dependency
called composite builds. I'm not sure if that would be your intention to
do, but that works if you specify t
Greetings,
I have a Gradle rookie question which I was not able to solve after
searching the internet for a considerable amount of time, maybe you can
help.
I recently decided to upgrade all of my Java projects in netbeans from Ant
to Gradle build and after a bit of a learning curve it works, exce
