Sorry strike the previous comment.
My MANIFEST.MF file for the plugin that is providing the missing class files looks like this:
Manifest-Version: 1.0 Export-Package: gov.nasa.rapid.v2,gov.nasa.rapid.v2.agent,gov.nasa.rap id.v2.exception,gov.nasa.rapid.v2.message,gov.nasa.rapid.v2.message.c ollector,gov.nasa.rapid.v2.message.command,gov.nasa.rapid.v2.message. helpers,gov.nasa.rapid.v2.message.holders,gov.nasa.rapid.v2.message.p ublisher,gov.nasa.rapid.v2.preferences,gov.nasa.rapid.v2.system,gov.n asa.rapid.v2.system.builtin,gov.nasa.rapid.v2.util Bundle-ActivationPolicy: lazy Built-By: tecohen Bundle-Name: RAPID Java Bindings v2 Created-By: Apache Maven Bundle-RequiredExecutionEnvironment: JavaSE-1.6 Require-Bundle: org.eclipse.core.runtime,gov.nasa.dds.rti;visibility:= reexport,gov.nasa.rapid.idl.dds;visibility:=reexport,gov.nasa.util;vi sibility:=reexport Build-Jdk: 1.6.0_33 Bundle-Version: 1.0.0.201302042334 Bundle-ManifestVersion: 2 Bundle-Activator: gov.nasa.rapid.v2.RapidV2Activator Bundle-SymbolicName: gov.nasa.rapid.v2 Archiver-Version: Plexus Archiver
The PDE generated similar MANIFEST.MF file looks like this: Manifest-Version: 1.0 Export-Package: gov.nasa.rapid.v2,gov.nasa.rapid.v2.agent,gov.nasa.rap id.v2.exception,gov.nasa.rapid.v2.message,gov.nasa.rapid.v2.message.c ollector,gov.nasa.rapid.v2.message.command,gov.nasa.rapid.v2.message. helpers,gov.nasa.rapid.v2.message.holders,gov.nasa.rapid.v2.message.p ublisher,gov.nasa.rapid.v2.preferences,gov.nasa.rapid.v2.system,gov.n asa.rapid.v2.system.builtin,gov.nasa.rapid.v2.util Require-Bundle: org.eclipse.core.runtime,gov.nasa.dds.rti;visibility:= reexport,gov.nasa.rapid.idl.dds;visibility:=reexport,gov.nasa.util;vi sibility:=reexport Bundle-ActivationPolicy: lazy Bundle-Version: 1.0.0.201302041435 Bundle-Name: RAPID Java Bindings v2 Bundle-Activator: gov.nasa.rapid.v2.RapidV2Activator Bundle-ManifestVersion: 2 Bundle-SymbolicName: gov.nasa.rapid.v2 Bundle-RequiredExecutionEnvironment: JavaSE-1.6
There may also be differences in the generated config.ini file. Any more tips? Thanks! Tamar
Hi Wim Thanks for the suggestion. I have done so with the plugin that cannot seem to provide the required Java class, and indeed it contains the expected class files in the correct directory. Interestingly enough I note there is a MANIFEST.MF file at the root, but in META-INF there is a maven directory and a maven.mf file. Tamar
HI Tamar,
Check every exported jar. If the size is low (e.g. 1K) then open it to see if it has the expected content. If not then check your build.properties to see if you have exported everything.
Regards,
Wim
|