Yes, I opened
https://bugs.eclipse.org/bugs/show_bug.cgi?id=509929 and
have a rough prototype for doing such checking automatically.
The checks include loading the repo, ensuring that the IUs really
exist in that repo, and trying to do a resolution against each
version of Eclipse (ensuring that the IUs will really install into
that version of Eclipse). But I've been busy since then and have
not had time to progress further on it... And I'm concerned that
there is not enough resource on the foundation side of things to
actually follow up on any work I do in this regard... My desire
was to add a page to the installer where users could choose
additional marketplace-based functionality to install in their
IDE, but that's a lot of work as well, and I'm not keen to provide
such a feature when the quality of what's listed in so poor...
On 10.07.2017 16:43, Mikaël Barbero
wrote:
If think that Ed Merks already proposed something to identify such
bad entries (as a side effect of getting info about p2 IUs of all
marketplace entries).
Ed, do you confirm? It's something that run on a
regular basis, right?
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.