I think the issue is that the whole product has to offer an update.. individual features in the product cannot publish updates independently that will be discovered by the update check. This is both a good thing and a bad thing, depending on your perspective.. I don't think there is a silver bullet solution to this (but I would also enjoy hearing proposals :).
John
----- Original message -----
From: Pascal Rapicault <pascal@xxxxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
To: cross-project-issues-dev@xxxxxxxxxxx
Cc:
Subject: Re: [cross-project-issues-dev] New components in Mars.1 (was Re: Eclipse Mars 1 RC4 issue with Buildship / workspace prompt)
Date: Wed, Sep 23, 2015 3:19 PM
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
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
