That makes sense. I can see that on "plugins/org.locationtech.udig.libs/META-INF/MANIFEST.MF" there is this section "Export Package:" with mention to individual exported/published packages. That doesn't seems to be human-hand made or editable, so it might be the place where Eclipse save the settings you mentioned.
I am loading the project in Eclipse Indigo 64 bit now (OSX 10.9 Java 1.7). It's going to
take forever just to do the "Resolving Target Definition" and then "Set
as Target Platform" so I am going to turn off the energy saving settings and let it run overnight.
Date: Thu, 29 May 2014 11:57:19 +1000
From: jody.garnett@xxxxxxxxx
To: udig-dev@xxxxxxxxxxxxxxxx
Subject: Re: [udig-dev] problem adding a lib
There is perhaps one more thing to do ... the eclipse class loader really likes to lock down interactions between "bundles".
In addition to listing the file in MANIFEST.MF (which you can do from the "runtime" tab of the MANIFEST.MF editor) you also need to explicitly say what packages you want to "publish" from the bundle.
So not only are they restricting what jars are available on the class path, they are also providing fine grain control over what packages in those jars are "public" :)
So back to the runtime tab in the MANIFEST.MF editor, and check on the right hand side for the list of published packages. There is a button to add more packages to this list.
--
Jody
_______________________________________________
udig-dev mailing list
udig-dev@xxxxxxxxxxxxxxxx
https://locationtech.org/mailman/listinfo/udig-dev