netbeans-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shevek (JIRA)" <>
Subject [jira] [Created] (NETBEANS-2987) Indirect gradle classpath change not recognized
Date Thu, 15 Aug 2019 01:05:00 GMT
Shevek created NETBEANS-2987:

             Summary: Indirect gradle classpath change not recognized
                 Key: NETBEANS-2987
             Project: NetBeans
          Issue Type: Bug
            Reporter: Shevek

Have four projects, A, B, C, D.
A depends on B, depends on C.
A depends on D.

1. Delete A -> D.
1a. A auto-reloads the gradle path.
1b. Now A fails to compile because it's missing the class from D.
2. Add C depends on D.
2a. C autoreloads the gradle path.

1. A should compile, since it now has access to D again, but does not.
2. fix-imports in A cannot see any classes in C.
3. A netbeans restart does NOT fix this.
4. Removing .gradle/nb-cache and restarting DOES fix this.

A bit fishy, this one, but I'm fairly sure this is what's going on. I think the intermediate
project B is a required element of this bug.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

For further information about the NetBeans mailing lists, visit:

View raw message