ipse.org<mailto:p2-dev@eclipse.org>
Subject: Re: [p2-dev] RCP check-for-update standard behavior
Mickael,
I in no way suggested that Julien should do this; I expect that he doesn't.
The point is that there are many way to specify requirements and I know the EPP
packages have changed ho
installed, it will also be taken into account
by the check for update.
Regards,
Julien
From: p2-dev-boun...@eclipse.org [mailto:p2-dev-boun...@eclipse.org] On Behalf
Of Ed Merks
Sent: jeudi 21 mars 2019 12:01
To: p2-dev@eclipse.org
Subject: Re: [p2-dev] RCP check-for-update standard behavior
Mickael,
I in no way suggested that Julien should do this; I expect that he
doesn't. The point is that there are many way to specify requirements
and I know the EPP packages have changed how it does this over time. So
the underlying point is that even if he locks in specific versions for
Hi Ed,
On Thu, Mar 21, 2019 at 11:36 AM Ed Merks wrote:
> But generally the p2 metadata produced for a feature.xml will lock in very
> specific versions of their included bundles and features which prevents
> those from being updated to a different version. That's sometimes annoying
> and then
Hi Julien,
It seems like it's something you already understand enough to set up an
experiment and see by yourself ;)
Marketplace is not related, what you want to clarify is
1. Whether added p2 repo affect the Check for Updates behavior (I believe
answer is yes, ie if your extra repo adds new
