RE: [smila-user] Inconsistent hierarchy for classes in different bundles

[<Juergen.Schumacher@xxxxxxxxxxx>]

Hi,

> -----Original Message-----
> From: smila-user-bounces@xxxxxxxxxxx [mailto:smila-user-
> bounces@xxxxxxxxxxx] On Behalf Of Giorgio Sironi
> Sent: Friday, April 16, 2010 12:35 PM
> To: smila-user@xxxxxxxxxxx
> Subject: [smila-user] Inconsistent hierarchy for classes in different
> bundles
> 
> Hi,
> I'm using SMILA 0.7 both in its binary form and its source taken from
> the 0.7 svn tag.
> I've set up the integration environment like described in the wiki,
> with the smila folder as my Plugin Development platform.
> I've checked out org.eclipse.smila.processing.bpel.test, which has a
> Import-Package directive towards org.eclipse.smila.test; however I
> cannot get it to run without adding in MANIFEST.MF:
>  Import-Package: junit.framework
> which I have previously copied in plugins/ and reloaded as suggested.
> org.eclipse.smila.processing.bpel.test never references JUnit 3
> classes, only subclasses like DeclarativeServiceTestCase which are
> defined in org.eclipse.smila.test; so I thought importing also JUnit
> was unnecessary, but without the additional import Eclipse says
> "Inconsistent class hierarchy" and it does not compile.
> Am I doing something wrong? All my build paths never reference
> anything then the code/ folder of the current package and the
> "Required dependencies" automatically synchronized to the manifest by
> Eclipse. It seems strange I had to import packages imported by other
> imported packages; it's supposed to be transitive.

Sorry, but I think I don't quite understand your problem. The MANIFEST.MF in
my ....bpel.test bundle checked out from trunk (but that should be identical
to the version tagged as 0.7) already contains an

Import-Package: junit.framework;version="[3.8.0,4.0.0)",

I'm using this in the development environment, not the integration environment,
but here it works. So where do you have to add something?

I think the PDE sometimes behaves a bit strange. Especially after migrating to 
Galileo I had to add some import-package statements for packages imported by 
imported bundles, which was not necessary with Ganymede before. So we just did 
it without asking further because it didn't cause any other problems. I did not
do any further research then which one is correct with respect to the OSGi
spec. Sorry, I don't know anything more helpful about this stuff myself (-;

Kind Regards,
Juergen.