|p2 repository contains binaries which is not included. [message #1044954]
||Fri, 19 April 2013 14:59
| Tobias Bertelsen
Registered: October 2011
When I build a p2 repository based on a feature, it includes binaries and metadata for all products in my workspace. This creates problems, since the metadata and configuration of the products is erroneous.
To me it seems to be a bug. Is there a fix or a workaround?
The (simlified) situation
I am creating two p2 repositories: product.p2 and extra.p2
product.p2 contains my core product, i.e. the rcp and a feature with my product bundles, including the one where my .product files are located (see below). This repository is only used during build.
- org.eclipse.rcp (feature)
- my.product.feature (feature)
- my.product.bundle (bundle)
- my.definition.product (.product file)
extra.p2 contains some extra features, which might be updated later on. This site is published after the build.
- my.functionality.feature (feature)
I set up a workspace including everything i need for the build, and the use Buckminster headless to build the two p2 repositories. The extra p2 repository only contains the features and bundle specified, but additionally it contains binary files and some meta-data for my product. The meta-data incomplete. It e.g. lacks configuration for the SimpleConfigurator.
I then use the p2-director to install my product and the extra features. The p2-director scan the p2 repositories in random order. If it scans my extra repository first, the resulting product will have an invalid configuration, e.g., SimpleConfigurator is not set to autostart. This makes my build nondeterministic
It is therefore a serious problem for me, that the extra p2-site contains binaries and meta-data for all products in my workspace, even though they are not included in the p2-repository.
Is there a way to turn this off or correct this.
Powered by FUDForum
. Page generated in 0.50052 seconds