Eclipse Community Forums: Equinox » Eclipse Plug-in Project vs. Plug-in in Target Platform

Home » Eclipse Projects » Equinox » Eclipse Plug-in Project vs. Plug-in in Target Platform

Eclipse Plug-in Project vs. Plug-in in Target Platform [message #111616]

Mon, 09 June 2008 15:48

Eclipse User

Originally posted by: chopkins.cra.com

I have a plug-in that has been developed by an external client. I use the
plug-in as a project within my workspace and all my plug-ins that depend on
it are working fine. However, if I try to export that plug-in and include it
as part of my defined Target Platform (so I don't have to have it as a
project in my workspace) then weird things happen. This is related to my
other post about mission constraints. Here's what happens:

* When I include the plug-in as a project in my workspace, everything
compiles and runs fine
* I then try the following:
1. Export that plug-in (exporting it as a directory and not a .jar as it
contains embedded jar files that Eclipse doesn't like)
2. close the project
3. Add the exported plug-in to my defined Target Platform
* This results in my plug-in projects being able to compile but when I try
to run I get a Validation Error that says:

Missing Constraint: Import-Package: com.draper.jaguar.datacore; version =
"0.0.0"

Why can my plugin projects see those packages at compile time but not run
time? Is there some configuration difference that I'm missing?

Thanks,
Chris

Re: Eclipse Plug-in Project vs. Plug-in in Target Platform [message #111624 is a reply to message #111616]

Tue, 10 June 2008 03:30

Eclipse User

Originally posted by: ekkehard.gentz-software.de

chris,

seems that your plug-in has an
Import-Package: com.draper.jaguar.datacore
in the MANIFEST.MF

so there must be another bundle exporting this package to make your bundle
happy

there's always a difference between compile-time and run-time ;-)

the compiler is satisfied if all needed classes are in project classpath
at compile-time

if you run the bundle from your target platform the bundle-classpath has
to find all and your Import-Package says that there must be a package but
it wasn't found.
what if you install your bundle from console and test with diag ?

if you dont need the package always, then you can make it optional

ekke

Christopher Hopkins wrote:

.... but when I try
> to run I get a Validation Error that says:

> Missing Constraint: Import-Package: com.draper.jaguar.datacore; version =
> "0.0.0"

> Why can my plugin projects see those packages at compile time but not run
> time? Is there some configuration difference that I'm missing?

> Thanks,
> Chris

Previous Topic:	BundleActivator invalid
Next Topic:	Framework and Bundle level security policy

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 27 04:36:33 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter