[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [p2-dev] Publishing units with whole manifest
|
Hi,
The code still has a reduced set of "interestingKeys" in BundlesAction:411-426 (toManifestString() method).
It seems this change is fairly old. Is it possible that tycho uses older p2.publisher version?
Or indeed this is configurable somehow and the touchpoint data is modified at a later point?
I'm curious about that because when integrating Virgo with p2 it became clear that the manifest of some artifacts or at least parts of it needs to be published as well in order to transfer the "uses" package data it contains and extract it later when deploying but prior executing the provisioning plan to feed it in an Equinox resolver.
So if there is a standard way to configure publishing the whole manifest it would be helpful to understand how its done.
If there isn't then what do you think is the best way to transfer extra manifest data from publishing to the resolution phase?
An idea can be to publish properties to the IUs containing just the "uses" data or maybe a new "uses" xml element. Obviously reverting to publish the whole manifest again is a step backwards.
Thanks,
Borislav
2011/7/12 Борислав Капукаранов
<b.kapukaranov@xxxxxxxxx>
Hi,
While browsing Eclipse's hudson server I stumbled upon some maven/tycho build jobs that publish p2 repositories with units containing the whole artifact manifest.
I thought publishing the whole manifest is removed from p2 due to performance issues. I'm pretty sure I saw it in the code too.
Is it still possible to activate it somehow, considering these repositories I found?
Thanks
Borislav
