[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] [prov] manifest changes

I have reverted this change and also gone through the p2 bundles to ensure
that the EEs are set correctly. There is currently a problem in the way
that we compute the classpath w.r.t. EEs so we need to leave the higher EEs
first in the manifest for now.

For reference, the bug is described here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=219979

Also it is important to note that when you change the EE in the bundle
manifest editor, you must also update the classpath for the project using
the link below the EE section. If you don't, then you will have an EE
listed first in the manifest (e.g. Foundation 1.1) but PDE will be using a
different one to compile the project in your workspace (e.g. 1.4) and when
a new VM (e.g. Foundation 1.1) is added to the builder, then the build will
fail because you may be referencing methods not found in those libraries. I
have updated the p2 bundles to have matching manifests and classpath files.

Thanks.


equinox-dev-bounces@xxxxxxxxxxx wrote on 02/21/2008 03:47:04 PM:

>
> I have released a change to the manifest file for the
> org.eclipse.equinox.p2.artifact.repository project so Kim can test the
> Foundation EE in the build. If you have this project (and this change)
> loaded into your workspace and a Foundation 1.1 VM set up, it will also
> require that you have a project like Xerces also in your workspace.
Xerces
> is already in the project set file so you should be good, but I just
wanted
> to give you a heads up in case you see strange errors about not finding
XML
> classes.
>
>