Bug 125 - Should auto-release parent tree (1GEPF6J)
Summary: Should auto-release parent tree (1GEPF6J)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P5 normal (vote)
Target Milestone: 2.0 M6   Edit
Assignee: Kevin McGuire CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 21:36 EDT by Kevin McGuire CLA
Modified: 2002-05-23 21:20 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin McGuire CLA 2001-10-10 21:36:51 EDT 
1. create a new java project with a main class
2. sync the main class
3. try to release just that resource

Get the no-lock error.
If you then pick the project to release you still can't (I think you'ld need to resync the project).

NOTES:

KM (6/5/01 7:50:22 PM)
	Verified, still exists in 118.

Jean-Michel (06/06/2001 9:40:11 AM)
	We should refresh parents when showing the sync view. I think that John
	already auto-releases parents if they are outgoing creations. But when you
	call sync on one resource only that resource is refreshed, ui doesn't know that
	parents are outgoing creations.

JohnA (6/7/2001 8:46:00 PM)
	Isn't this a fairly costly thing to do, just for supporting that uncommon case?

JohnA (6/7/2001 9:22:36 PM)
	Added support, tested, it works.  We can discuss implications with JML tomorrow.

JohnA (6/8/2001 11:06:21 AM)
	Support had side-effects.  Bailing out.  All parents of the released file were showing
	up as incoming creations on next attempt to synchronize.

JohnA (6/9/2001 3:26:52 PM)
	Moving to future.
Comment 1 DJ Houghton CLA 2001-10-29 16:51:40 EST 
(6/9/2001 3:26:48 PM)
{important/ ?hr}

PRODUCT VERSION:

117
Comment 2 Kevin McGuire CLA 2002-04-17 16:02:29 EDT 
now works