--- Leif Frenzel <himself@...> wrote:
> Ouch, yes, I had that problem, too. Cost me weeks,
> and I never figured out
> what happened. The problem disappeared when I
> switched to a fresh Eclipse
> 3.0 (final) installation. (I had been using the
> various milestones and RCs
> before.) On that occasion, I decided not to import
> my old preference
> settings and workspace, but just use a clean new
> installation, copied all
> project folders to a new directory, and imported
> them as 'existing
> projects'. After that everything went fine.
I'm using 3.0 final running on a windows box and a
linux box. Both show the problem. With the windows box
I copied the project folders and imported them as
existing projects; then, besides the ocaml.core
errors, there appeared new ones related to
dependencies on the common.core and common.ui
> My best guess as to what the problem is is this: the
> export build consists
> of a generated Ant build file for every project.
> (You can generate the build
> files if you right click the feature.xml and select
> PDE Tools > Create Ant
> Build File.)
Funny enough, I generated the build file and ran it
manually as an ant build, and everything went fine. It
didn't package the feature, though, but built jars of
all the plugins and the feature, dropping them at
their respective projects' directory.
> I had the suspicion, that
> it had to do with the
> path structure on my Windows machine, because I had
> all my project folders
> in a top-level folder (C:\eclipsefp). But I'm not
> sure about that.
On my windows box I have most projects under the
workspace directory, and the ocaml, ocaml.core and
ocaml.ui plugins in a separate top-level directory. On
the linux box everything is in the workspace.
s, Andrei de A. Formiga
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.