[OS-JIRA] Created: (WOL-1026) HTML/WOD auto-completion breaks with certain workspace setup

From: JIRA (Timo)
Date: Wed Jun 17 2009 - 05:01:18 EDT

  • Next message: David Avendasora: "Re: WOLips Version"

    HTML/WOD auto-completion breaks with certain workspace setup
    ------------------------------------------------------------

                     Key: WOL-1026
                     URL: http://issues.objectstyle.org/jira/browse/WOL-1026
                 Project: WOProject/WOLips
              Issue Type: Bug
        Affects Versions: AgentJ
             Environment: 5811, eclipse 3.4.2
                Reporter: Timo Höpfner
             Attachments: stacktrace.txt

    I have a situation where HTML/WOD auto-completion stops working when I use a certain workspace setup. I don't know if it's a WOLips or an eclipse bug or if I'm just misusing something here.

    Our projects are organized in a similar folder structure as in Wonder. In the root dir there are folders for Frameworks, Projects, etc. The root folder is set up as a non-java eclipse project, the actual apps/frameworks are eclipse projects within sub folders thereof. I do this to use SVN to add/checkout new projects wihin that folder structure and to work with non-project resources (docs, utilities, ...).

    I usually check out the root folder as (non-java) project into my workspace and then import the real projects using "Import -> Existing Projects into Workspace". So from eclipse's point of view, there are two paths to each resource. This used to work fine for several years and still works for Wonder, which I've setup in the same fashion.

    However, a while ago WOD auto-completion stopped working as soon as the root of our project structure is added as project to the workspace. I get an exception in the console upon first triggering of auto completion in the HTML editor:

    Java Model Exception: Java Model Status [ProDataSystems does not exist]

    Where "ProDataSystems" is the non-java "top level" project. I'll add the complete stack trace as an attachment. It appears to me that at some point the non-java project is interpreted as java project and then somethiing essential (for a java project) is not found.

    As mentioned before, I don't have this problem with Wonder. I've compared the ".project" files of my top level project and the Wonder top level project and except for the name they are identical.
    Digging around in the worspace's ".metadata" folder, one maybe significant difference I see is, that in

    <workspace>/.metadata/.plugins/org.eclipse.core.resources/.projects/ProDataSystems

    there is no ".location" file, whereas Wonder has one.

    -- 
    This message is automatically generated by JIRA.
    -
    If you think it was sent incorrectly contact one of the administrators: http://issues.objectstyle.org/jira/secure/Administrators.jspa
    -
    For more information on JIRA, see: http://www.atlassian.com/software/jira
    



    This archive was generated by hypermail 2.0.0 : Wed Jun 17 2009 - 05:02:30 EDT