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 would the build process find the other project?
>
> For example I have thi
n?
Thanks again, Matthias
Am Do., 26. Dez. 2019 um 16:35 Uhr schrieb Laszlo Kishalmi <
laszlo.kisha...@gmail.com>:
> 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,
>
> t
://docs.gradle.org/current/userguide/composite_builds.html
>
> On 12/22/19 6:40 AM, Dr. Matthias Laux wrote:
> > 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
>
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,
oject.hasProperty('runArgs')) {
> args = project.getProperty('runArgs').tokenize(' ')
> }
>
> }
> On 11/27/19 6:24 AM, Dr. Matthias Laux wrote:
>
> Hello,
>
> I'm starting to lose hope in this ... I got my class library using OpenJPA
> to work nicely in N
Hello,
I'm starting to lose hope in this ... I got my class library using OpenJPA
to work nicely in Netbeans using Ant support and storing stuff in the
backend Derby database.
Then I decided to move to the much newer Gradle and - after a bit of a
learning curve - all builds work find. The one
