[ https://issues.apache.org/jira/browse/NETBEANS-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shevek updated NETBEANS-2987: ----------------------------- Description: Have four projects, A, B, C, D. A depends on B, 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. Now we have A>B>C>D. 2b. C autoreloads the gradle path. Result: 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. was: Have four projects, A, B, C, D. A depends on B, 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. Result: 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. > Indirect gradle classpath change not recognized > ----------------------------------------------- > > Key: NETBEANS-2987 > URL: https://issues.apache.org/jira/browse/NETBEANS-2987 > Project: NetBeans > Issue Type: Bug > Reporter: Shevek > Priority: Major > > Have four projects, A, B, C, D. > A depends on B, 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. Now we have A>B>C>D. > 2b. C autoreloads the gradle path. > Result: > 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 (v7.6.14#76016) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists