Attila Kelemen

I can't reproduce the issue. Where exactly do you provide this "-Plib" argument, so that NB knows about it? gradle.properties or in the global settings of NB? If NB jumps...

What happens for task execution doesn't really matter, the only thing what is relevant is what happens when NB evaluates the script. So, adding anything to the built-in tasks will...

The wiki page [Development](https://github.com/kelemen/netbeans-gradle-project/wiki/Development) describes how to setup the project for debugging. If the project was set up, you can look at the following classes/methods (this model parsing is probably...

The content of the lib shouldn't matter. What could if the jar produced is not the output of the *jar* task. Or symlinks in paths can cause all kinds of...

That seems to explain the issue: because of the "..", the owner project of the built artifact was wrong. I'm not sure I could easily fix that because it is...

If the size itself is not a problem for you, then I wouldn't worry. Each file stores the model of the associated subproject, so that if you restart NB and...

Projects are rather independent in NB, so I cannot just easily share data amongst them. I could do that through some global cache but I don't think reducing the memory...

Thanks for these details. For overall speed: Though, I can't see your case: According to my experience project loading time is heavily dominated by the configuration resolution which is not...

There is another thing to consider and see if it improves your situation considerably: - Add the `-J-XX:+UseG1GC -J-XX:+UseStringDeduplication` arguments to your `/etc/netbeans.conf` under the `netbeans_default_options` key. You will need...

While it looks like that all projects are loaded independently, it is not exactly the case. What actually happens is that after the first subproject of a multi-project build gets...