| Unpacking choosen bundles after installation [message #677142] |
Tue, 07 June 2011 16:55  |
|
Dear friends of p2,
I've a serious problem with the installation of one of our features from
our update site. We need to unpack one bundle since it contains an
executable binary.
Hence, we marked this bundle to be unpacked after the installation in
the feature.xml. This works well during our p2-based product build.
This information however seems to be ignored during the installation
from the update site (which in fact is a p2 repository), or the
unpacking process fails silently.
Does anybody has any clue about that?
cheers,
Christian
|
|
|
| Re: Unpacking choosen bundles after installation [message #1008313 is a reply to message #677142] |
Mon, 11 February 2013 21:25  |
|
Hi,
I found this question in the newsgroup:
On 07.06.11 18:55, Christian Schneider wrote:
> I've a serious problem with the installation of one of our features from
> our update site. We need to unpack one bundle since it contains an
> executable binary.
>
> Hence, we marked this bundle to be unpacked after the installation in
> the feature.xml. This works well during our p2-based product build.
>
> This information however seems to be ignored during the installation
> from the update site (which in fact is a p2 repository), or the
> unpacking process fails silently.
>
> Does anybody has any clue about that?
I have exactly the same problem. In my case, the bundle, feature, and
repository is built with maven/tycho 0.16.0. I also have a bundle which
contains native binaries, thus it must be unpacked. But it is not.
Is there some setting I'm missing in the category.xml, the feature.xml,
or in tycho?
Regards,
Jens
|
|
|
|
Powered by
FUDForum. Page generated in 0.02968 seconds
] 
Search
Help
Register
Login
Home
