Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pde-dev] Target Definition update/resolution problems


Am 08.07.2014 um 22:18 schrieb Curtis Windatt <Curtis_Windatt@xxxxxxxxxx>:
No, PDE will not ping the repository to check for newer versions unless the sequence number is increased.  Pressing the update button (with the fix) will ping the remote repository and take the latest version (without changing the 0.0.0 setting).

Good to know. AFAIK in 4.3 it replaced the 0.0.0 with the latest version.

If that workflow is a problem, please open a bug.  The likely solution would be to make a p2 target location dirty on creation if it has an IU with 0.0.0.  This would make the behaviour similar to 4.3.  Note that if such a target was set as the target platform, the p2 repositories would be contacted on startup (when the PDE models were created), possibly causing delays in the UI.

Actually, the behavior does make a lot sense. I always wanted to have more control when PDE goes out to the remote repos. Knowing that it will only when you click the "update" button is good (I think). Maybe it’s now time to have a "reload" button for the whole target definition in the target editor? 

Btw, will the reload button in the preferences also cause a fetch of newer versions from remote repositories if 0.0.0 is being used?

-Gunnar

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx






Back to the top