|
|
| Re: How is installFeature action supposed to work? [message #899357 is a reply to message #899306] |
Tue, 31 July 2012 14:24   |
 Thorsten Meinl
Messages: 85
Registered: July 2009 |
Member |
|
|
Hi Hendrik,
Could you point me to or send me more details on how you did this?
Thanks,
Thorsten
Am 31.07.2012 14:30, schrieb Henrik Lindberg:
> We had the same/similar issue in cloudsmith / geppetto @ github. Our
> solution was to ship a "run once" bundle that used the p2 API to make
> the modifications.
>
> Regards
> - henrik
>
> On 2012-30-07 17:53, Thorsten Meinl wrote:
>> Hi all,
>>
>> We are currently facing the problem of turning an implicitly installed
>> feature (from a feature dependency) into a root feature via an update to
>> the RCP application. I though that could be accomplished with the
>> installFeature touchpoint action, but this does not work, because the
>> feature to be installed by this action must be among the artifacts of
>> the current feature. This is obviously not the case, I have never seen
>> an feature.group being the artifact of another feature (is this even
>> possible?). This is a bit disappointing since this seemed to be the only
>> way of accomplishing the task. Two question:
>>
>> 1. Why is installFeature restricted to artifacts of the current IU
>> (which in almost all cases does not make sense I believe)?
>> 2. Is there another way of turning a non-root IU into a root IU without
>> explicitly installing the IU?
>>
>> The overall goal is to make the non-root IU uninstallable, which isn't
>> possible if it isn't a root IU (only).
>>
>> Cheers,
>>
>> Thorsten
>>
>
|
|
|
| Re: How is installFeature action supposed to work? [message #899586 is a reply to message #899357] |
Wed, 01 August 2012 14:08 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
On 2012-31-07 16:24, Thorsten Meinl wrote:
> Hi Hendrik,
>
> Could you point me to or send me more details on how you did this?
>
The code for the "run once" is here:
https://github.com/cloudsmith/geppetto/blob/master/org.cloudsmith.geppetto.onetimeinstall/src/org/cloudsmith/geppetto/onetimeinstall/Activator.java
Hope that helps you.
- henrik
> Thanks,
>
> Thorsten
>
> Am 31.07.2012 14:30, schrieb Henrik Lindberg:
>> We had the same/similar issue in cloudsmith / geppetto @ github. Our
>> solution was to ship a "run once" bundle that used the p2 API to make
>> the modifications.
>>
>> Regards
>> - henrik
>>
>> On 2012-30-07 17:53, Thorsten Meinl wrote:
>>> Hi all,
>>>
>>> We are currently facing the problem of turning an implicitly installed
>>> feature (from a feature dependency) into a root feature via an update to
>>> the RCP application. I though that could be accomplished with the
>>> installFeature touchpoint action, but this does not work, because the
>>> feature to be installed by this action must be among the artifacts of
>>> the current feature. This is obviously not the case, I have never seen
>>> an feature.group being the artifact of another feature (is this even
>>> possible?). This is a bit disappointing since this seemed to be the only
>>> way of accomplishing the task. Two question:
>>>
>>> 1. Why is installFeature restricted to artifacts of the current IU
>>> (which in almost all cases does not make sense I believe)?
>>> 2. Is there another way of turning a non-root IU into a root IU without
>>> explicitly installing the IU?
>>>
>>> The overall goal is to make the non-root IU uninstallable, which isn't
>>> possible if it isn't a root IU (only).
>>>
>>> Cheers,
>>>
>>> Thorsten
>>>
>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03430 seconds