[
https://issues.apache.org/jira/browse/NETBEANS-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845440#comment-16845440
]
Laszlo Kishalmi commented on NETBEANS-2371:
-------------------------------------------
The reason, why I ask for help, is that I found out that the Maven projects
using some IDE level project locks when requesting for new classpath
information. That kind of locking is missing from the Gradle implementation and
it could cause problems like this. However implementing it wrong could cause
that the whole IDE hangs on a deadlock (like I hit in one of my first
implementations).
> Gradle projects not properly loaded
> -----------------------------------
>
> Key: NETBEANS-2371
> URL: https://issues.apache.org/jira/browse/NETBEANS-2371
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
> Affects Versions: 11.0
> Environment: Netbeans 11
> Gradle 5
> Java 11
> Reporter: Netbeans User 2019
> Assignee: Laszlo Kishalmi
> Priority: Major
>
> - gradle module (plugin) has problem to resolve dependencies in multi project
> as seems I can removed reds only if I go over each one subproject and do
> clean and build (clean and build on root has no affects) and additionally it
> seems that for some test resources even this was not enough, but it seems
> that works old trick so creation folder and adding some new class (possible
> even delete) and possibly with including "refresh" from Action items window.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
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
