Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 106102

Summary: [Examples] Error creating resource in project that is checked in (using Pessimistic Simple Provider)
Product: [Eclipse Project] Platform Reporter: Kim Kelley <kdkelley>
Component: TeamAssignee: Platform Team Inbox <platform-team-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 Keywords: helpwanted
Version: 3.2   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug

Description Kim Kelley CLA 2005-08-04 17:32:33 EDT
We are using the Pessimistic Simple Provider to do testing on our Team Support,
and came across this problem in Linux that seems to be a general Eclipse
problem.  If you try to create any new resource in a project that has been
checked-in, you get a nasty error dialog and are unable to complete the wizard.

Steps to reproduce:
- install the Pessimistic Simple Provider plugin for eclipse if you don't have
it already (org.eclipse.team.examples.filesystem)
- Create a new simple project
- Share the new project: Right-click on the project and select Team -> Share
Project.. -> Pessimistic Simple Provider.  
- Check in the new project: Right-click and select Team -> check-in
- Now try to create a new simple file in this project
When you press finish on the "New" wizard, you will see an error dialog that
says something like "Parent of resource foo is marked as read-only".  Depending
on the resource type you try to create, you may also see an exception in the
.log (see below).

I have tried this with several project and artifact types, and all seem to have
the same problem.

Running on SuSe Linux Enterprise Server 9

Sample exception in the .log:
Java Model Exception: Core Exception [code 277] Parent of resource:
/home/wsadie_ui/workspaces/kim-dev/TestJavaProj/trew is marked as read-o
nly.
        at
org.eclipse.jdt.internal.core.JavaModelOperation.createFolder(JavaModelOperation.java:270)
        at
org.eclipse.jdt.internal.core.CreatePackageFragmentOperation.executeOperation(CreatePackageFragmentOperation.java:83)
        at
org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:700)
        at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1673)
        at
org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:744)
        at
org.eclipse.jdt.internal.core.PackageFragmentRoot.createPackageFragment(PackageFragmentRoot.java:313)
        at
org.eclipse.jdt.ui.wizards.NewTypeWizardPage.createType(NewTypeWizardPage.java:1412)
        at
org.eclipse.jdt.internal.ui.wizards.NewClassCreationWizard.finishPage(NewClassCreationWizard.java:55)
        at
org.eclipse.jdt.internal.ui.wizards.NewElementWizard$2.run(NewElementWizard.java:108)
        at
org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:34)
        at
org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:700)
        at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1673)
        at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:3246)
        at
org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:65)
        at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Caused by: org.eclipse.core.internal.resources.ResourceException: Parent of
resource: /home/wsadie_ui/workspaces/kim-dev/TestJavaProj/trew i
s marked as read-only.
        at
org.eclipse.core.internal.localstore.FileSystemStore.writeFolder(FileSystemStore.java:406)
        at
org.eclipse.core.internal.localstore.FileSystemResourceManager.write(FileSystemResourceMan
Comment 1 Eclipse Genie CLA 2019-07-28 10:21:28 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.