[
https://issues.apache.org/jira/browse/NETBEANS-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845407#comment-16845407
]
Shevek commented on NETBEANS-2371:
----------------------------------
Thing is, if what I see is classpath related, I'd expect it to consistently
error on a given classpath-derived symbol everywhere that symbol is consumed in
the downstream module, which it doesn't, and I'd expect it not to resolve by
rescanning one file, which it does. This is just randomly flagging errors on
files scattered throughout the codebase with no rhyme or reason. I just looked,
and I have like 10 of these right now, in about 50,000 Java files. So I think I
may be seeing something else.
I am also running on high-concurrency machines: 12-64 cores, so I do tend to
hit races where present. :)
> 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
