|Plugins installed using aTarget Definition are not properly installed [message #1041767]
||Mon, 15 April 2013 10:43
| Kyle Girard
Registered: March 2012
I've created a local p2 repository to contain all my third party dependencies. I've converted all the 3rd party jars to be osgi bundles, some bundles need to be unpacked when installed (Eclipse-BundleShape: dir), some have dependencies on system.bundle, others have Eclipse-Buddy headers etc. The jars have all the correct headers in their manifest files when I look at them on the site. However, after specifying the site in a target definition file the plugin that gets installed is not the same as the plugin on the site. The manifest has been rewritten and dependencies are altered, headers I require in the manifest have been removed, the plugin that is supposed to be unpacked is unpacked but only directories that include .class files are unpacked, others are left out.
What do I have to do to ensure that the plugin in the p2 repository is the one installed using the target definition? I've created the p2 site using both the build site button in the site.xml editor and using tycho eclipse-repository. I though that there was some metadata of some sort not being written but in either case the result is the same? What am I missing?
I've looked at the libraries in the orbit repository with slightly older versions and my manifests look the same as theirs for a couple of the libraries.. minus the signing.
Powered by FUDForum
. Page generated in 0.02787 seconds