Ther seems to be a tool scanning the plugin.xml files already in someway
and generate the html output, it sounds reasonable to extend this part
to look for @ProviderType in a text file ending with .java I don't think
we need a full blown parsing here.
Am 28.03.21 um 08:12 schrieb Mickael Istria:
On Sun, Mar 28, 2021 at 8:01 AM Christoph Läubrich
<[email protected] <mailto:[email protected]>> wrote:
I think the most simple aproach would be to makr Interfaces that are
consumed by the Platform with @ProviderType [1], this could then be
scanned by tools and generate the list you have mentioned automatically.
[1]
https://docs.osgi.org/specification/osgi.core/7.0.0@ProviderTyp/framework.api.html#org.osgi.annotation.versioning
<https://docs.osgi.org/specification/osgi.core/7.0.0/framework.api.html#org.osgi.annotation.versioning>
Adding @ProviderType is a good idea.
However, I don't buy the idea that "scanned by tools and generate list"
is simpler than maintaining it manually for the moment; unless those
tools and generators are already existing. Are they?
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
_______________________________________________
platform-dev mailing list
[email protected]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
[email protected]
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
