Community
Participate
Working Groups
AK (6/15/01 7:53:56 PM) create two packages in one source folder p and p.p1 now, if you modify a file in p.p1 the > mark shows in for p as well NOTES:
moved to 'active'
PRODUCT VERSION: 124
*** Bug 3855 has been marked as a duplicate of this bug. ***
*** Bug 4051 has been marked as a duplicate of this bug. ***
*** Bug 3526 has been marked as a duplicate of this bug. ***
*** Bug 4040 has been marked as a duplicate of this bug. ***
The design has changed i.e. version info provided by vcm via decorator but the problem is still here. This is a major issue because this is confusing for the user (marking a package to have changes while he did not change anything in there). Leaving P2 but would even vote to become P1
I agree on the importance but the issue is that the decoration is done by the CVSDecorator using the IResource adapter. It therefore can only know about the resource hierarchy. Similarly, the Java views cannot know about the CVS decorations. All they do is to map LabelProviderChangedEvents for IResources back to IJavaElements. One idea was to show two different dirty indicators on containers: - "logically" dirty - the container contains dirty children - "physically" dirty - the container is "otherwise" dirty To make this happen would require VCM support for hooking into the CVS decoration. This is unlikely to happen for 2.0 (unless Kevin disagrees). Finally, as a weak argument - the problem only shows up when the "Compute Deep Outgoing change for folders" is on. Opt to do nothing for 2.0
I would love to solve this but we have no solution for 2.0.
Kevin, any plans to give JDT the change to influence this ?
Our choices at present are: 1. We can stop showing dirty indicators on parents. To find out if you have projects with changes, you'ld need to perform a query. This has certain performance gains as well since you don't have to check the dirty status for all elements of a project (expensive and doesn't scale as projects increase in size). 2. Something else which understands the logical parenting in the packages view. All we have here is the problem description; we have no solution to propose as yet, but at least have time to think about it now. This is the deluxe solution although it doesn't avoid the performance issue cited above.
*** Bug 21263 has been marked as a duplicate of this bug. ***
*** Bug 13426 has been marked as a duplicate of this bug. ***
*** Bug 10011 has been marked as a duplicate of this bug. ***
*** Bug 24388 has been marked as a duplicate of this bug. ***
*** Bug 22430 has been marked as a duplicate of this bug. ***
Kevin... In reference to your list of possibilities on 2002-07-25, how about a third possibility, where a task is created and added to the task view for each dirty resource. This would save the user from having to search for dirty resources. Granted, this might not be the best solution since the number of dirty resources could be large. A number of quick-fixes could be created for dirty resources including rolling back to the latest in the stream or local history, commiting the changes, etc.
Simon, we had thought about tasks for this, although our experience with using them for denoting new (unshared) resources is that they don't play well (they are lost amoungst the errors, people don't look for them, etc). We would probably require a combination of things.
*** Bug 25584 has been marked as a duplicate of this bug. ***
I've downgraded from P2 since no action for 2.1 which we are closing on.
*** Bug 36222 has been marked as a duplicate of this bug. ***
*** Bug 42492 has been marked as a duplicate of this bug. ***
*** Bug 45706 has been marked as a duplicate of this bug. ***
*** Bug 47584 has been marked as a duplicate of this bug. ***
*** Bug 50041 has been marked as a duplicate of this bug. ***
If im not mistaken, this applies to all OS. Also, this is fine for Hierachy layout, but the problem is strickly with Flat layout!? What exactly is "show version info?" The problem I am experiencing is with the CVS status icons.
*** Bug 72001 has been marked as a duplicate of this bug. ***
*** Bug 74866 has been marked as a duplicate of this bug. ***
Fix released to HEAD
Had to back out of this due to bug 86493.
Created attachment 25770 [details] Patch to add proper patch decoration once dependencies are fixed
*** Bug 111044 has been marked as a duplicate of this bug. ***
Fix released to HEAD. Packages are now decorated properly.
*** Bug 125851 has been marked as a duplicate of this bug. ***
*** Bug 36292 has been marked as a duplicate of this bug. ***