[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[photran] Problem in using C/C++ perspective
|
Hello, everybody.
I've recently tried to install and use Photran, both under Linux and Windows,
both as a standalone application and as an Eclipse feature, and in all cases
I've experienced what follows.
Version of Eclipse: 3.3.0 Build M20070921-1145
3.3.1.1 Build M20071023-1652
Version of Photran: 4.0b3 w. CDT 4.0.2.200711280800
Problem: in closing a C++ project (i.e., working under the C++ perspective)
after the (successful) build, Photran complains about the following:
________________
'Synchronizing Photran VPG (Time of error: dd month yyy hh:mm:ss)
Reason: org.eclipse.core.internal.resources.ResourceException: Resource
'/dir_of_the_project' is not open.
Details: An internal error occurred during "Synchronizing Photran VPG".
org.eclipse.core.internal.resources.ResourceException: Resource
'/dir_of_the_project' is not open.
_______________
This has happened repeatedly (or rather, always), as I said both with the
'Full' distribution and with the 'Photran feature' installed into an Eclipse
Europa 3.3.1.1 release (Build M20071023-1652). I add that the corresponding
option (in the preference menu) is disabled.
I append herein the lines from the log in which Photran 'explains' what's
happened:
________________________________________________________________________________________________________
!ENTRY org.eclipse.core.jobs 4 2 2008-01-09 10:57:24.500
!MESSAGE An internal error occurred during: "Synchronizing Photran VPG".
!STACK 0
java.lang.Error: org.eclipse.core.internal.resources.ResourceException:
Resource '/polar' is not open.
at
org.eclipse.photran.core.vpg.PhotranVPG.shouldProcessProject(PhotranVPG.java:146)
at
bz.over.vpg.eclipse.EclipseVPG$VPGResourceDeltaVisitor.visit(EclipseVPG.java:245)
at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:67)
at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:76)
at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:48)
at
bz.over.vpg.eclipse.EclipseVPG$VPGResourceDeltaJob.runInWorkspace(EclipseVPG.java:212)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.eclipse.core.internal.resources.ResourceException: Resource
'/polar' is not open.
at
org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:97)
at org.eclipse.core.internal.resources.Project.hasNature(Project.java:467)
at
org.eclipse.photran.core.vpg.PhotranVPG.shouldProcessProject(PhotranVPG.java:141)
... 7 more
!ENTRY org.eclipse.core.jobs 4 2 2008-01-09 11:07:28.187
!MESSAGE An internal error occurred during: "Synchronizing Photran VPG".
!STACK 0
java.lang.Error: org.eclipse.core.internal.resources.ResourceException:
Resource '/polar' is not open.
at
org.eclipse.photran.core.vpg.PhotranVPG.shouldProcessProject(PhotranVPG.java:146)
at
bz.over.vpg.eclipse.EclipseVPG$VPGResourceDeltaVisitor.visit(EclipseVPG.java:245)
at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:67)
at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:76)
at
org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:48)
at
bz.over.vpg.eclipse.EclipseVPG$VPGResourceDeltaJob.runInWorkspace(EclipseVPG.java:212)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.eclipse.core.internal.resources.ResourceException: Resource
'/polar' is not open.
at
org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:97)
at org.eclipse.core.internal.resources.Project.hasNature(Project.java:467)
at
org.eclipse.photran.core.vpg.PhotranVPG.shouldProcessProject(PhotranVPG.java:141)
... 7 more
________________________________________________________________________________________________________
Any idea of what it could cause it? For what I've been able to understand by
searching through the archives here, on the list, it would seem that such a
problem has never been experienced before.
Thank you in advance for your attention. Any suggestion will be welcome...
schroeder