Bug 108199 - Checkout of a large project prevent new pde project creation
Summary: Checkout of a large project prevent new pde project creation
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: investigate
Depends on: 128709
Blocks:
  Show dependency tree
 
Reported: 2005-08-27 15:02 EDT by Pascal Rapicault CLA
Modified: 2023-07-20 12:41 EDT (History)
5 users (show)

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 Pascal Rapicault CLA 2005-08-27 15:02:24 EDT 
3.1M1

- Go to the repository exploration perspective
- Expend the projects in the CVS repositories views and select a project that
has a very significant size. Check out this project into the workspace. This
will eventually result in one project in thr workspace, however don't wait for
the checkout to complete and proceed to the next step
- From inside the repo perspective, create a new PDE project, pick the default
options and click finish. 
- The creation of the project seems to the locked by the fetch.

I'm a bit surprised since from a workspace point of view, those two operations
should be exclusive since they both work on a different project.

It might be a PDE pb.
Comment 1 Michael Valenta CLA 2005-09-20 12:14:55 EDT 
It is PDE via the Java project creation that is obtaining the workspace root 
as the scheduling rule and thus blocking on the CVS checkout. Moving to PDE to 
consider whether obtaining the workspace root rule is required for this 
operation.
Comment 2 Chris Aniszczyk CLA 2008-01-17 18:10:31 EST 
Any love from Poland :)?
Comment 3 Michael Valenta CLA 2008-01-18 07:45:57 EST 
There's no pont looking at this bug until bug 128709 is resolved since, due to bug 128709, the checkout acquires the workspace root rule.
Comment 4 Eclipse Genie CLA 2019-08-08 11:36:02 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Eclipse Genie CLA 2021-07-29 17:08:40 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 6 Eclipse Genie CLA 2023-07-20 12:41:35 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.