When I click on a maven project under 'Projects' and do 'Show Changes' I get different (wrong) results as when I click on the exact same folder of the maven project in 'Favorites'.
Product Version = NetBeans IDE 7.3 RC2 (Build 201302050851)
Operating System = Linux version 3.5.0-24-generic running on amd64
Java; VM; Vendor = 1.7.0_15
Runtime = Java HotSpot(TM) 64-Bit Server VM 23.7-b01
Created attachment 131647 [details]
Anyway, the result should be correct. Project node is a logical node that includes its source groups (src, tests, external libraries etc.) and *not* the project folder. So the results may be different because both the times you're trying to look for changes of different folders.
Created attachment 131652 [details]
Created attachment 131653 [details]
Created attachment 131654 [details]
You are just to fast with answering :)
> What screenshot?
> Anyway, the result should be correct. Project node is a logical node that includes its source groups (src, tests, external libraries etc.) and *not* the project folder. So the results may be different because both the times you're trying to look for changes of different folders.
Screenshot 1 + 3 show that the path of the maven eircom project in 'Projects' and the folder 'jtf' in 'Favorites' are actually the same. Screenshot 2 + 3 show though that the 'Show Changes' action shows different results. Screenshot 3 is correct. I checked with an external commandline client.
I tried 'Cleanup working copy', close/open Netbeans, close/open the eircom project but it didn't make any difference
Exactly what i'm talking about. It's a logical node and does not contain maven submodules. Discussed in bug #159543
*** This bug has been marked as a duplicate of bug 159543 ***
To bypass the logic of parent and sub projects you're either supposed to go to Favorites or simply select all the projects you want to commit (parent and all its subprojects).
OK - that is a totally NOT obvious behaviour, since everybody working with svn 'knows' that if I do a 'Show Changes' on a parent node, I *will* get all changes of the levels below. The current behaviour does not really make sense for SVN.
If the project would exist of some modules that are part of the current folder hierarchy and some modules that are not in the same folder hierarchy and would perform an SVN action I would only expect the ones IN the current folder hierarchy be part of the SVN 'update/commit', since this is what SVN does....