Re: [platform-core-dev] MANIFEST.MF Validation Issues

[Konrad Kolosowski <konradk@xxxxxxxxxx>]

There has been improvements in manifest
validator after M6.  Can you try Eclipse when it is out M7 (or one
of today's builds)?  If the errors are still reported, open a bug
against PDE-UI.

Konrad Kolosowski

"Scott Delap" <SDelap@xxxxxxxxxxxxxx>
Sent by: platform-core-dev-bounces@xxxxxxxxxxx

05/13/2005 12:47 PM

Please respond to
"Eclipse Platform Core component developers list."

To	<platform-core-dev@xxxxxxxxxxx>
cc
Subject	[platform-core-dev] MANIFEST.MF Validation Issues

The project I'm working on started using
Eclipse 3.1 M6 as its base last week.  We have imported the Eclipse
plugins into our workspace in binary form.  Several projects have
errors when validating their manifests.  One specific example is org.eclipse.core.runtime.
 This plugin has classes in the root directory.  The validator
can't seem to handle this as a classpath and complains about the export
package lines.  I've also tried adding . and ./ as the bundle classpath
with no success.  As a work around I attempted jaring up the classes
and specifying this jar in the bundle classpath for each project.  This
resolves the validation errors.  However, I now receive the following
error when trying to startup my Eclipse based application:
 
java.lang.ClassNotFoundException: org.eclipse.core.runtime.adaptor.EclipseStarter
 at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
 at org.eclipse.core.launcher.Main.invokeFramework(Main.java:312)
 at org.eclipse.core.launcher.Main.basicRun(Main.java:268)
 at org.eclipse.core.launcher.Main.run(Main.java:942)
 at org.eclipse.core.launcher.Main.main(Main.java:926)
 
I am assuming this is due to changing the
osgi plugin to a jar to resolve its manifest errors.  Suggestions/comments
are very welcome.  Will M7 fix this?  Is there another way to
tack the manifest errors?  Is the manifest validation a bug?  Is
there a way to leave my jar changes in place and get everything to startup
right?
 
Scott_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-core-dev