> > <Export-Package>*</Export-Package> > > > FYI, when embedding dependencies use <_exportcontents> not > <Export-Package> > as explained here: > > > http://felix.apache.org/site/apache-felix-bundle-plugin-faq.ht > ml#ApacheFelixBundlePluginFAQ-WhenIembedadependencywhydoIseedu > plicatedcontent%3F
Umm... This actually creates private packages again, which I don't want. Every package should be exported. If I understand the feature right, it applies only if I have packages in my source code which match packages in my dependencies. Since I don't have any source code in that project, it shouldn't matter, right? > > > > Now the Eclipse RCP developer is telling me that Eclipse > doesn't like the > > MANIFEST format that Felix generates... weird! > > Have you ever heard of such problems? (He previously > created the MANIFEST > > by hand, putting every JAR and every package in its own line) > > > > sometimes a refresh (F5) is needed to get Eclipse in sync with the > file-system, if you run the build on the command line > otherwise double-click on the manifest then click on the > MANIFEST.MF tab and > it should show which lines it doesn't like > - then post the errors here (or perhaps capture a screenshot?) > > ( PS. don't use PDE Tools -> Organize Manifests... as that > will definitely > mess things up! ) > Well, there are 535 errors, so it would be a BIG screenshot ;-) There are these kinds of errors (one example for each): - Bundle 'ch.ipi.esv.client.serverlib' exporting package 'org.apache.commons.io.comparator' is unresolved - No available bundle exports package 'javax.interceptor' - Package 'com.google.inject.matcher' does not exist in this plug-in - Unsatisfied constraint: 'Import-Package: org.apache.commons.lang.math; version="2.4.0"' Now, I know that these packages do exist in the dependencies, so it's probably some kind of misconfiguration. One of the RCP developers mentioned that the 'uses:=' part might be the troublemaker...? Also, I'm generating an Eclipse PDE project as described on the Felix page, but really, it's a total mess. Only about a third of the dependencies are in the visible 'Referenced Libraries', about half of them use the M2_REPO environment variable, the rest is hard-coded as linked resource in the .project file, and of course all of them point to my local Maven repo instead of the project! Do you have any idea how I could force the Eclipse plugin to do the right thing? I see in the example that there seems to be a plugin.xml which I don't have, perhaps the path configuration is in there? Best regards, Eric --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
