lkishalmi commented on pull request #2747: URL: https://github.com/apache/netbeans/pull/2747#issuecomment-803592988
> > Make a difference between Gradle involved and heuristic based project loading > > During my last week discussions with @sdedic it showed few times that knowing whether the external view of a `org.netbeans.api.Project` is exact or just a heuristic is important. Well, that's associated with the project (information) quality flag FALLBACK > > > reload would happen on root project level. > > Good. It is my understanding that `gradle` is optimized for keeping structure of large projects in memory and then processing just the necessary part. Reloading on root level (if one can find where's the root?) seems like a good idea. Finding a root project shall work 99% of the time as Gradle now requires the root project having a settings Gradle script in it's directory (unless the settings script is specified from the command line, that's the remainder 1% maybe less projects). The intermediate project structure is harder to guess. Gradle just started to work in it's configuration caching which is at the moment not available for the IDEs to tap on. Some parts might be already cached though. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- 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
