Re: [cross-project-issues-dev] New components in Mars.1 (was Re: Eclipse Mars 1 RC4 issue with Buildship / workspace prompt)
Step 1 - test to see whether it works. Anecdotal evidence says it doesn't. Something about how the EPP packages are defined and built. Also projects need to make sure the URLs for maintenance p2 sites are correct and enabled by default.
The Check for Updates including the auto check feature itself works. We've used it for years in our commercial product. Just need to make sure everything is set up correctly for the packages.
I'm also not sure (and actually doubt) auto check is turned on in all the packages so that when users start them up and/or on regular intervals it does a check and prompts the user to install the updates.
This has to be the default behavior without the user having to do anything. That way the user could have installed Mars.1 and then when they start up they would have been prompted to install the update for Buildship any other feature that happened to have updates out by then.
We talked about this at the architecture call. Not sure it got captured in the minutes there. But this is the general idea.
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [cross-project-issues-dev-bounces@xxxxxxxxxxx] on behalf of Pascal Rapicault [pascal@xxxxxxxxxxxx]
Sent: Wednesday, September 23, 2015 3:18 PM
Subject: Re: [cross-project-issues-dev] New components in Mars.1 (was Re: Eclipse Mars 1 RC4 issue with Buildship / workspace prompt)
I was about to ask the same :)
On 15-09-23 02:54 PM, Mike Milinkovich wrote:
> On 23/09/2015 1:49 PM, Doug Schaefer wrote:
>> if we could ever get Check for Updates working properly, this
>> wouldn't have been such a big issue.
> Doug (or anyone)
> Is there a written proposal anywhere on how "Check for Updates" should
> be modified?
> Is there an existing consensus around such a proposal?
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit