[jbosstools-issues] [JBoss JIRA] Created: (JBIDE-4349) Patch to fix compilation on clean workspace under Eclipse 3.5

[Sean Flanigan (JIRA)]

Patch to fix compilation on clean workspace under Eclipse 3.5
-------------------------------------------------------------

                 Key: JBIDE-4349
                 URL: https://jira.jboss.org/jira/browse/JBIDE-4349
             Project: Tools (JBoss Tools)
          Issue Type: Patch
    Affects Versions: 3.1.0.M1
         Environment: Fedora 11 preview (x86_64)
            Reporter: Sean Flanigan
            Assignee: Nick Boldt


I've been having a lot of trouble getting trunk to compile under Eclipse 3.5 (M7 or RC1), using 3.5M7 build drivers as my target platform.  (I compile in a vanilla 3.5.x, not using the target platform.) If I compile in Eclipse 3.4.2 (fresh workspace), everything compiles, but if I use 3.5, I get these errors in my Problems view (even after a complete reload of the target platform and workspace clean):

      Description     Resource     Path Location Type
      The project was not built since its build path is incomplete. Cannot find the class file for org.eclipse.core.expressions.Expression. Fix the build path then try building this project org.jboss.tools.vpe            Unknown       Java Problem
      The project was not built since its build path is incomplete. Cannot find the class file for org.eclipse.core.net.proxy.IProxyService. Fix the build path then try building this project        org.jboss.tools.common.test          Unknown      Java Problem
      The project was not built since its build path is incomplete. Cannot find the class file for org.eclipse.jem.util.emf.workbench.ProjectUtilities. Fix the build path then try building this project     org.jboss.tools.seam.core        Unknown     Java Problem
      The project was not built since its build path is incomplete. Cannot find the class file for org.eclipse.ui.actions.SelectionListenerAction. Fix the build path then try building this project  org.jboss.tools.hibernate.ui.veditor            Unknown       Java Problem
      The type org.eclipse.core.expressions.Expression cannot be resolved. It is indirectly referenced from required .class files     VpeEditorPart.java   /org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor        line 1077       Java Problem
      The type org.eclipse.core.net.proxy.IProxyService cannot be resolved. It is indirectly referenced from required .class files    HttpUtilTest.java   /org.jboss.tools.common.test/src/org/jboss/tools/common/util/test  line 22   Java Problem
      The type org.eclipse.jem.util.emf.workbench.ProjectUtilities cannot be resolved. It is indirectly referenced from required .class files SeamUtil.java    /org.jboss.tools.seam.core/src/org/jboss/tools/seam/core    line 222    Java Problem
      The type org.eclipse.ui.actions.SelectionListenerAction cannot be resolved. It is indirectly referenced from required .class files      OpenSourceAction.java /org.jboss.tools.hibernate.ui.veditor/src/org/jboss/tools/hibernate/ui/veditor/editors/actions   line 61    Java Problem
      The type org.eclipse.wst.common.internal.emfworkbench.integration.EditModelNature cannot be resolved. It is indirectly referenced from required .class files    JstPublisher.java   /org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/publishers  line 317  Java Problem
      The project was not built since its build path is incomplete. Cannot find the class file for org.eclipse.wst.common.internal.emfworkbench.integration.EditModelNature. Fix the build path then try building this project        org.jboss.ide.eclipse.as.core      Unknown    Java Problem

I did have all of these classes in my workspace, so I was able to find their plugins, and add them to Require-Bundle in the manifests of the non-compiling plugins.  This fixed the compilation errors I was getting.  My patched manifests are attached.

As Nick said in IRC, these errors look like manifest problems hidden by the build (and other environments).

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