Home » Eclipse Projects » Oomph » Setup task execution on re-start
| Setup task execution on re-start [message #1730320] |
Sun, 24 April 2016 12:28  |
Eclipse User |
|
|
|
Hi,
I usually have the preference for skipping automatic task execution at
start-up turned off because otherwise I would download an enormous
Papyrus build into my PDE Target every time I re-start my workbench.
However, there are times when the workbench is re-started by Oomph.
When I specifically run the setup from the menu and that includes an
update of my installation (via p2 tasks), Oomph will automatically
re-start the workbench to finalize that update with the expectation
that then it will continue with the rest of the tasks prescribed by the
setup model. But because I have the automatic task execution skipping
preference set, that doesn't happen. I have to manually trigger the
setup again, deselect the p2 tasks that were already done, and then
complete the wizard.
I think it would make sense that the preference be ignored on the
occasion of this particular Oomph-initiated re-start. Is there already
an option to do this? Or perhaps the Oomph team would be interested in
receiving a contribution that makes it happen?
Thanks,
Christian
|
|
|
| Re: Setup task execution on re-start [message #1730340 is a reply to message #1730320] |
Mon, 25 April 2016 04:11  |
| Eclipse User |
|
|
|
Christian,
Comments below.
On 24.04.2016 18:28, Christian W. Damus wrote:
> Hi,
>
> I usually have the preference for skipping automatic task execution at
> start-up turned off because otherwise I would download an enormous
> Papyrus build into my PDE Target every time I re-start my workbench.
The PDE task shouldn't return isNeeded true on startup trigger if the
the target is already active and resolved.
>
> However, there are times when the workbench is re-started by Oomph.
> When I specifically run the setup from the menu and that includes an
> update of my installation (via p2 tasks), Oomph will automatically
> re-start the workbench to finalize that update with the expectation
> that then it will continue with the rest of the tasks prescribed by
> the setup model. But because I have the automatic task execution
> skipping preference set, that doesn't happen. I have to manually
> trigger the setup again, deselect the p2 tasks that were already done,
> and then complete the wizard.
I see. Certainly if you're restarting and there are outstanding tasks
to execute, we should consider that. Also the first time you launch,
but I think that works okay because the preference isn't applied to the
workspace until during that first time...
>
> I think it would make sense that the preference be ignored on the
> occasion of this particular Oomph-initiated re-start. Is there
> already an option to do this? Or perhaps the Oomph team would be
> interested in receiving a contribution that makes it happen?
Yes, it seems reasonable. We do store the outstanding tasks in a file,
so if that file is not empty, we could assume that the user want's those
automatically performed.
>
> Thanks,
>
> Christian
>
|
|
|
| Re: Setup task execution on re-start [message #1730367 is a reply to message #1730340] |
Mon, 25 April 2016 06:32 |
| Eclipse User |
|
|
|
I've changed this in https://bugs.eclipse.org/bugs/show_bug.cgi?id=492349
On 25.04.2016 10:11, Ed Merks wrote:
> Christian,
>
> Comments below.
>
> On 24.04.2016 18:28, Christian W. Damus wrote:
>> Hi,
>>
>> I usually have the preference for skipping automatic task execution
>> at start-up turned off because otherwise I would download an enormous
>> Papyrus build into my PDE Target every time I re-start my workbench.
> The PDE task shouldn't return isNeeded true on startup trigger if the
> the target is already active and resolved.
>>
>> However, there are times when the workbench is re-started by Oomph.
>> When I specifically run the setup from the menu and that includes an
>> update of my installation (via p2 tasks), Oomph will automatically
>> re-start the workbench to finalize that update with the expectation
>> that then it will continue with the rest of the tasks prescribed by
>> the setup model. But because I have the automatic task execution
>> skipping preference set, that doesn't happen. I have to manually
>> trigger the setup again, deselect the p2 tasks that were already
>> done, and then complete the wizard.
> I see. Certainly if you're restarting and there are outstanding tasks
> to execute, we should consider that. Also the first time you launch,
> but I think that works okay because the preference isn't applied to
> the workspace until during that first time...
>>
>> I think it would make sense that the preference be ignored on the
>> occasion of this particular Oomph-initiated re-start. Is there
>> already an option to do this? Or perhaps the Oomph team would be
>> interested in receiving a contribution that makes it happen?
> Yes, it seems reasonable. We do store the outstanding tasks in a
> file, so if that file is not empty, we could assume that the user
> want's those automatically performed.
>>
>> Thanks,
>>
>> Christian
>>
>
|
|
|
| Re: Setup task execution on re-start [message #1730396 is a reply to message #1730367] |
Mon, 25 April 2016 08:41 |
| Eclipse User |
|
|
|
Wow! Thanks, Ed.
cW
On 2016-04-25 10:32:28 +0000, Ed Merks said:
> I've changed this in https://bugs.eclipse.org/bugs/show_bug.cgi?id=492349
>
> On 25.04.2016 10:11, Ed Merks wrote:
>> Christian,
>>
>> Comments below.
>>
>> On 24.04.2016 18:28, Christian W. Damus wrote:
>>> Hi,
>>>
>>> I usually have the preference for skipping automatic task execution at
>>> start-up turned off because otherwise I would download an enormous
>>> Papyrus build into my PDE Target every time I re-start my workbench.
>> The PDE task shouldn't return isNeeded true on startup trigger if the
>> the target is already active and resolved.
>>>
>>> However, there are times when the workbench is re-started by Oomph.
>>> When I specifically run the setup from the menu and that includes an
>>> update of my installation (via p2 tasks), Oomph will automatically
>>> re-start the workbench to finalize that update with the expectation
>>> that then it will continue with the rest of the tasks prescribed by the
>>> setup model. But because I have the automatic task execution skipping
>>> preference set, that doesn't happen. I have to manually trigger the
>>> setup again, deselect the p2 tasks that were already done, and then
>>> complete the wizard.
>> I see. Certainly if you're restarting and there are outstanding tasks
>> to execute, we should consider that. Also the first time you launch,
>> but I think that works okay because the preference isn't applied to the
>> workspace until during that first time...
>>>
>>> I think it would make sense that the preference be ignored on the
>>> occasion of this particular Oomph-initiated re-start. Is there already
>>> an option to do this? Or perhaps the Oomph team would be interested in
>>> receiving a contribution that makes it happen?
>> Yes, it seems reasonable. We do store the outstanding tasks in a file,
>> so if that file is not empty, we could assume that the user want's
>> those automatically performed.
>>>
>>> Thanks,
>>>
>>> Christian
|
|
|
Goto Forum:
Current Time: Sun Sep 21 10:06:55 EDT 2025
Powered by FUDForum. Page generated in 0.03440 seconds |
Home