| Summary: | Exception in ProjectAnalyzer on project creation | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] M2T | Reporter: | Sven Efftinge <sven.efftinge> | ||||||
| Component: | Xpand | Assignee: | Darius Jockel <darius.jockel> | ||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | darius.jockel, m2t.xpand-inbox, sebastian.zarnekow | ||||||
| Version: | 0.8.0 | Flags: | sven.efftinge:
helios+
|
||||||
| Target Milestone: | M6 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||||
| Whiteboard: | |||||||||
| Bug Depends on: | |||||||||
| Bug Blocks: | 284019 | ||||||||
| Attachments: |
|
||||||||
|
Description
Sven Efftinge
Hello Sven. (In reply to comment #0) > When using the wizard from bug #284019, I get the following exception when > using creating a "workspace defaults" Sorry, but I can not reproduce the problem. Can you please provide more information? I tried two times to generate a example project with default settings, but without getting an exception. Regards I've seen this one, too after I upgraded my dev environment to 3.6 (In reply to comment #2) > I've seen this one, too after I upgraded my dev environment to 3.6 Ok. I run Eclipse 3.5.1 I will update my environment, too. Created attachment 157905 [details]
Patch
If an project is deleted from workspace but the contents are not deleted too,
the project wizard will throw an exception:
org.eclipse.core.internal.resources.ResourceException: Resource '/my.generator.project/META-INF' already exists.
(In reply to comment #2) > I've seen this one, too after I upgraded my dev environment to 3.6 I have updated my environment, too (Also I used the xtext projectset). But I can still not reproduce the error. All I got is a: org.eclipse.core.internal.resources.ResourceException (see last comment). (In reply to comment #0) This bug can only be caused by Runtime Eclipse Instances. If you delete a lot of projects and then you create a new project, the ProjectAnalyser will scan recursively all projects for metamodells. After the "bulk delete" the plugin projects from the "motherworkspace" (is it the right word?) return false on .exists() and force a refresh on this projects. This cause a ResourceException. Running a Eclipse with Xpand M5 installed do not cause this Exception. Therefore I would like to close this Bug. I thought I'd fixed that only last week. Is it really not happening in M5 or is it not happening with the current HEAD? (In reply to comment #7) > I thought I'd fixed that only last week. Is it really not happening in M5 or is > it not happening with the current HEAD? In HEAD I got the following exception: org.eclipse.core.internal.resources.ResourceException: Resource '/.org.eclipse.jdt.core.external.folders/.link6' does not exist. at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:319) at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:196) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:49) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:106) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:90) at org.eclipse.xtend.typesystem.emf.ui.ProjectAnalyzer.loadMetamodelsForProject(ProjectAnalyzer.java:128) at org.eclipse.xtend.typesystem.emf.ui.ProjectAnalyzer.run(ProjectAnalyzer.java:90) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) But only in a Runtime Eclipse (In reply to comment #8) > In HEAD I got the following exception: > org.eclipse.core.internal.resources.ResourceException: Resource > '/.org.eclipse.jdt.core.external.folders/.link6' does not exist. > > But only in a Runtime Eclipse That's another one which we have to fix. The one I fixed is : java.lang.IllegalArgumentException: Attempted to beginRule: P/.org.eclipse.jdt.core.external.folders, does not match outer scope rule: P/my.generator.project_ws_defaults *** Bug 298641 has been marked as a duplicate of this bug. *** Created attachment 159331 [details] Patch for the ResourceException Patch fixed the ResourceException (see comment 8) (In reply to comment #7) > I thought I'd fixed that only last week. Yes, it is fixed. Bug resolved before Xpand 1.2 release date => Closing |