t;
> > I'm not sure how your project is set up, since I normally don't use the
> > term "module" in gradle projects.
> >
> >
> >
> > Sent from my Galaxy
> >
> >
> > Original message
> >
ect8
>>
>> > sub-sub-project1
>>
>> > sub-sub-project2
>>
>> > sub-sub-project3
>>
>> > sub-sub-project4
>>
>> > sub-sub-project5
>>
>> > sub-project9
>>
&g
x27;m not sure how your project is set up, since I normally don't use the
> > term "module" in gradle projects.
> >
> >
> >
> > Sent from my Galaxy
> >
> >
> > Original message
> > From: Thomas Kellere
Greetings,
Well, yes, I've had gradle issues in the past due to work projects. It is
rather important that
the people trying to fix issue X have a way to ensure that they are using code
that invokes
issue X to see if they are actually fixing issue X.
_*Nobody*_ expects you to publish your n
gt; "module" in gradle projects.
>
>
>
> Sent from my Galaxy
>
>
> Original message
> From: Thomas Kellerer
> Date: 6/26/23 01:17 (GMT-06:00)
> To: users@netbeans.apache.org
> Subject: Re: Gradle modules and dependency scanning
>
> Any id
ate:
6/26/23 01:17 (GMT-06:00) To: users@netbeans.apache.org Subject: Re: Gradle
modules and dependency scanning Any ideas?Thomas Kellerer schrieb am 13.06.2023
um 11:36:> I noticed one problem (in NetBeans 17 but it also happens with 18)
with the Gradle integration.>> I am working on a
Any ideas?
Thomas Kellerer schrieb am 13.06.2023 um 11:36:
> I noticed one problem (in NetBeans 17 but it also happens with 18) with the
> Gradle integration.
>
> I am working on a multi-module project (with 40 modules) using Gradle.
>
> Dependencies to classes in modules that are not currently o
I noticed one problem (in NetBeans 17 but it also happens with 18) with the
Gradle integration.
I am working on a multi-module project (with 40 modules) using Gradle.
Dependencies to classes in modules that are not currently open in the Projects
window are not detected.
NetBeans marks classes u
