| problem with embedded jar [message #540295] |
Tue, 15 June 2010 10:40  |
Eclipse User |
|
|
|
Hello,
I write a plugin A that has an import-package dependency.
The needed package comes from an other plugin B, which uses a third
embedded .jar C. C is referenced in the MANIFEST.MF of B using
Bundle-ClassPath: C.jar
My target platform is defined through a platform definition file and
references a galileo mirror containing B.
This way the eclipse-ide is not able to resolve the needed package. I
see B as entry in the Plug-in Dependencies of A, but there is also an
error: "The import org.eclipse... cannot be resolved".
My workaround is to import B as binary project into my workspace. Now
the package could be resolved. But I don't want to import all plugins
with embedded jars into the workspace.
Where is my mistake? Is there an other way to resolve such packages?
I tested it with 3.5.2 and 3.6.0.RC4
An example for this behavior is the org.eclipse.equinox.servletbridge
bundle.
Regards,
Lars
|
|
|
|
| Re: problem with embedded jar [message #540442 is a reply to message #540356] |
Wed, 16 June 2010 03:34  |
| Eclipse User |
|
|
|
Hello Andrew,
On 15.06.2010 21:06, Andrew Niefer wrote:
> The problem is likely that the compiler doesn't support having nested jars
> on its classpath. At runtime OSGi will take care of the nested jar
> automatically, but at development time you need the nested jar extracted to
> disk.
>
> I don't think there is any better workaround than the one you have.
Thank you for the information.
Regards,
Lars
|
|
|
| Re: problem with embedded jar [message #606066 is a reply to message #540295] |
Tue, 15 June 2010 15:06 |
| Eclipse User |
|
|
|
The problem is likely that the compiler doesn't support having nested jars
on its classpath. At runtime OSGi will take care of the nested jar
automatically, but at development time you need the nested jar extracted to
disk.
I don't think there is any better workaround than the one you have.
-Andrew
Lars Fischer wrote:
> Hello,
>
> I write a plugin A that has an import-package dependency.
> The needed package comes from an other plugin B, which uses a third
> embedded .jar C. C is referenced in the MANIFEST.MF of B using
> Bundle-ClassPath: C.jar
>
> My target platform is defined through a platform definition file and
> references a galileo mirror containing B.
>
> This way the eclipse-ide is not able to resolve the needed package. I
> see B as entry in the Plug-in Dependencies of A, but there is also an
> error: "The import org.eclipse... cannot be resolved".
>
> My workaround is to import B as binary project into my workspace. Now
> the package could be resolved. But I don't want to import all plugins
> with embedded jars into the workspace.
>
> Where is my mistake? Is there an other way to resolve such packages?
> I tested it with 3.5.2 and 3.6.0.RC4
>
> An example for this behavior is the org.eclipse.equinox.servletbridge
> bundle.
>
> Regards,
> Lars
|
|
|
| Re: problem with embedded jar [message #606072 is a reply to message #540356] |
Wed, 16 June 2010 03:34 |
| Eclipse User |
|
|
|
Hello Andrew,
On 15.06.2010 21:06, Andrew Niefer wrote:
> The problem is likely that the compiler doesn't support having nested jars
> on its classpath. At runtime OSGi will take care of the nested jar
> automatically, but at development time you need the nested jar extracted to
> disk.
>
> I don't think there is any better workaround than the one you have.
Thank you for the information.
Regards,
Lars
|
|
|
Powered by
FUDForum. Page generated in 0.04131 seconds
Home