• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 1191 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS5.1 project import problems

gbl
Intellectual 400 points

On some PCs and for some projects CCS5.1 reports this error when a project shall be imported:

What does this error mean? When I click 'ok' at a first glance everything seems to be ok, but links to source files are empty in the project.

I work in a ClearCase environment using the latest ClearCase Plugin for Eclipse.

  • 0 in reply to Ki
    Intellectual 400 points

    Hi,

    short overview:

    The not existing resources are caused by the fact that the project files were checked in after a successful build. When importing a project to another PC of course the build results do not exist yet.

    The complete log file is attached.

    2500.eclipse2.log
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    !ENTRY org.eclipse.cdt.core 4 0 2011-11-15 08:01:10.154
    !MESSAGE Error: assertion failed: Operation was not prepared.
    !STACK 0
    org.eclipse.core.runtime.AssertionFailedException: assertion failed: Operation was not prepared.
    at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
    at org.eclipse.core.internal.resources.Workspace.beginOperation(Workspace.java:367)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2340)
    at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.runAtomic(CProjectDescriptionManager.java:498)
    at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.runWspModification(CProjectDescriptionManager.java:463)
    at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.runWspModification(CProjectDescriptionManager.java:433)
    at org.eclipse.cdt.internal.core.settings.model.CExternalSettingsManager.handleEvent(CExternalSettingsManager.java:620)
    at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.notifyListeners(CProjectDescriptionManager.java:2170)
    at org.eclipse.cdt.internal.core.settings.model.AbstractCProjectDescriptionStorage.fireLoadedEvent(AbstractCProjectDescriptionStorage.java:268)
    at org.eclipse.cdt.internal.core.settings.model.xml.XmlProjectDescriptionStorage.getProjectDescription(XmlProjectDescriptionStorage.java:255)
    at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescriptionInternal(CProjectDescriptionManager.java:416)
    at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescription(CProjectDescriptionManager.java:398)
    at org.eclipse.cdt.managedbuilder.core.ManagedBuildManager.findBuildInfo(ManagedBuildManager.java:2709)
    at org.eclipse.cdt.managedbuilder.core.ManagedBuildManager.getBuildInfo(ManagedBuildManager.java:2970)
    at com.ti.common.project.core.util.CTIProjectCoreUtils.getBuildInfo(CTIProjectCoreUtils.java:132)
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Can you recognize something from the details of 'Error: assertion failed: Operation was not prepared.'?

  • 0 in reply to gbl
    Intellectual 400 points

    This is blocking us more and more - do you have any idea what the problem could be?

  • 0 in reply to gbl
    TI__Genius 9175 points

    gbl,

    This turned out to be a strange Eclipse bug (or design limitation).  I've implemented a code work-around for it, and it will be available with CCSv5.1.1, which is currently scheduled for end of January 2012.

    Unfortunately, I can't think of any easy way for you to work-around it in the meantime.  This happens to any project that has dependencies on other projects, and that generates an OUT-file that's external to the project.  So, one work-around would be to change the project so that it generates the OUT-file physically within the build-directory (which is the default behaviour).

    - Baltasar