Well, I can't show the real project (customer project with NDA). And I can't
just create a project of that size (35 projects, 550K lines of code).
And besides I don't have a Github account.
The problem is, that basically every problem I have with NetBeans and Gradle
only happens on bigger projects (and not with some tiny example projects.
It would be a lot more helpful if NetBeans offered some diagnostic data that
would allow investigating such a problem. It's pretty unrealistic to as every
user that has a problem to publish their projects.
I thought Gradle uses the term "module" for projects that consist of multiple
sub-projects, but apparently I was wrong.
The layout is:
main_project
sub-project1
sub-sub-project1
sub-sub-project2
sub-project2
sub-project3
sub-sub-project1
sub-sub-project2
sub-sub-project3
sub-sub-project4
sub-sub-project5
sub-sub-project6
sub-sub-project7
sub-sub-project8
sub-sub-project9
sub-sub-project10
sub-sub-project11
sub-sub-project12
sub-sub-project13
sub-sub-project14
sub-sub-project15
sub-project4
sub-project5
sub-project6
sub-project7
sub-sub-project1
sub-sub-project2
sub-sub-project3
sub-sub-project4
sub-sub-project5
sub-sub-project6
sub-sub-project7
sub-sub-project8
sub-sub-project8
sub-project8
sub-sub-project1
sub-sub-project2
sub-sub-project3
sub-sub-project4
sub-sub-project5
sub-project9
sub-project10
sub-project11
sub-project12
sub-sub-project1
sub-sub-project2
sub-project13
For those sub-projects that aren't recognized I can see the following entries
in the NetBeans logfile:
INFO [org.netbeans.modules.gradle.loaders.GradleProjectLoaderImpl]: Load
aiming EVALUATED for Unloaded Gradle Project:
GradleFiles[projectDir=C:\Projects\******\main\commons,
rootDir=C:\Projects\*******\main]
Thomas
Mark A. Flacy schrieb am 26.06.2023 um 13:47:
> Create a simple example in GitHub or GitLab so that people have something to
> test against.
>
> 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 --------
> From: Thomas Kellerer <[email protected]>
> Date: 6/26/23 01:17 (GMT-06:00)
> To: [email protected]
> 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 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 using classes from a non-opened module with an error
>> ("ClassNotFound"), even though the class is available to Gradle when building
>>
>> As soon as I open the module containing the "missing" class, and reload the
>> referencing module, the error badges go away.
>>
>> However I don't really want to have all those 40 modules open all the time
>> to keep the "Projects" window clean, but the fact that most modules will be
>> marked as erroneous, makes this a bit annoying.
>>
>> Is there anything I can do, to make NetBeans recognize the classes from
>> non-opened modules?
>>
>> The Maven integration does not have this problem (although I have to admit
>> that most Maven projects I work on have a lot fewer modules than 40)
>>
>> Regards
>> Thomas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
