| How to force "Project Set Import" task to run always at Eclipse startup? [message #1729107] |
Mon, 11 April 2016 05:01  |
Eclipse User |
|
|
|
What's the criteria do decide which setup tasks run only at very first run (like Project Set Import, Copy Resources, etc.) and which setup tasks run always when Eclipse starts up (like Preferences, Launch Configs, Build Projects, etc.) ?
In the configuration I only see the Excluded Triggers, but not any option to force to include in some trigger.
The reason for this is that I would like to have the "Project Set Import" setup task to run always when Eclipse starts up. This way, it would automatically import new projects that are added to the psf file. In my case, the psf is being versioned in the Git repository.
Preferably, the task could even not run automatically, but be available for selection, as it happen with the current "Launch Config" that I have.
Is this possible?
|
|
|
| Re: How to force "Project Set Import" task to run always at Eclipse startup? [message #1729111 is a reply to message #1729107] |
Mon, 11 April 2016 05:44  |
| Eclipse User |
|
|
|
Silvestre,
Comments below.
On 11.04.2016 11:01, Silvestre Martins wrote:
> What's the criteria do decide which setup tasks run only at very first
> run (like Project Set Import, Copy Resources, etc.) and which setup
> tasks run always when Eclipse starts up (like Preferences, Launch
> Configs, Build Projects, etc.) ?
Neither of those two tasks are designed to run only the very first
time. It's a question of how is "isNeeded" determine...
> In the configuration I only see the Excluded Triggers, but not any
> option to force to include in some trigger.
That's what I mean, it's more a question of how is isNeeded computed for
the task. If it's not excluded by the trigger, isNeeded will be called,
and if it's needed it's it will be available to run, and if not, then
it's disabled.
>
> The reason for this is that I would like to have the "Project Set
> Import" setup task to run always when Eclipse starts up. This way, it
> would automatically import new projects that are added to the psf
> file. In my case, the psf is being versioned in the Git repository.
That specific tasks keeps a digest of the *.psf so if that file changes,
the task should return isNeeded true again.
>
> Preferably, the task could even not run automatically, but be
> available for selection, as it happen with the current "Launch Config"
> that I have.
It should just work.
>
> Is this possible?
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.19361 seconds
Home