Carsten,
I would be cautious about adding an artifact repository without actually
testing (i.e., loading, which can take very long) the artifact
repository to see if that URL is indeed also an artifact repository.
Of course most everyone creates colocated repositories, but p2 is more
flexible.
Regards,
Ed
On 05.03.2020 18:11, Carsten Reckord wrote:
I noticed that for the update check we only ever load the metadata
repository [...] we now have an update site list with just a metadata repo and
no
corresponding artifact repo, which would completely explain the observed
errors.
Now I'm wondering if we should attempt to fix the update site list
retroactively, i.e. scan for all metadata repos in the list that don't have a
corresponding artifact repo, and add it. Theoretically, there could be cases
where there is no 1:1 mapping between the two, but I think the common case is
that both should exist.
Opinions?
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
