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

Bug 312060

Summary:	Changing project to JetProject via wizard causes damaged project when .project file is read only
Product:	z_Archived	Reporter:	Florian Quadt <f.quadt>
Component:	Jet	Assignee:	Project Inbox <m2t.jet-inbox>
Status:	NEW ---	QA Contact:
Severity:	minor
Priority:	P3	CC:	f.quadt, pelder.eclipse
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Florian Quadt

2010-05-07 09:35:35 EDT

Build Identifier: 20100218-1602

If a java project has a read only project file and you try to add jet nature with a wizard, the wizard generates a templates directory and presumably mark the project as jet project but obviously cannot add jet project nature. 
Because the buildcommand and project nature missing in project file jet-development does not work.
If you try to add jet nature via wizard again, the project isn't listed in the wizard page where you select projects.
To fix the project you have to manually edit the project file and add nature and buildcommand.
To mark project file as read is unusual but revision control sometimes changes files behaviour.

fix proposal: promt user to change files access behaviour, like in many other cases in eclipse.

Reproducible: Always

Steps to Reproduce:
1. new Java Project
2. mark project file as read only (like some revision control does)
3. try to change project nature via wizard