[ 
https://issues.apache.org/jira/browse/NETBEANS-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862632#comment-16862632
 ] 

Laszlo Kishalmi commented on NETBEANS-2665:
-------------------------------------------

Well, the observation is good. It was designed that way. One of the my problem 
with the other plugin was that it was a real memory hog for large projects, so 
I went on treating subprojects individually. Putting the overhead of 
re-scanning the root project in the hands of the just emerging Gradle daemon. 
It actually hurts projects like: 
[https://github.com/shevek/simple-xml-serializers] as everything is defined in 
the build.gradle of the root project. NetBeans is listening on the changes of 
the root project build script and the project build script so eventually 
changing the root script is going to cause a reload of all subprojects.

Probably it would be the best if we could work with both ways and let the user 
choose between them by project. Though it would be a heavy lifting. The other 
way around is to restructure the build scripts as it is recommended in Gradle 
or in the way Gradle doing that (having a separate folder for build scripts, 
but one script for a sub-project).

> Gradle support loading subprojects individualy, rather than loading root
> ------------------------------------------------------------------------
>
>                 Key: NETBEANS-2665
>                 URL: https://issues.apache.org/jira/browse/NETBEANS-2665
>             Project: NetBeans
>          Issue Type: Bug
>          Components: projects - Gradle
>    Affects Versions: 11.0
>            Reporter: Shevek
>            Assignee: Laszlo Kishalmi
>            Priority: Major
>
> It appears that the gradle plugin is configuring and loading each subproject 
> of a multi-module project individually, rather than loading the root project 
> and querying subprojects.
> The upshot of this is that loading/executing/whatever Gradle 50 or 60 times 
> per subproject takes a few minutes, whereas loading the root project once 
> takes about 10 seconds.
> The old Gradle plugin, I think, was somewhat faster at this, as it loaded the 
> root project and inspected that hierarchically.
> This is an educated guess based on messages in the status bar - please feel 
> free to just close if I'm wrong.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Reply via email to