Sv: Sv: RFR: JMC-6555 Convert JOverflow plugin to SWT

[Marcus Hirt]

Hi Mario,

The problem is that the JavaFX bundles aren't proper OSGi bundles exposed on any pre-existing update site - they get exposed to the Tycho build through the local update site, together with other such third-party dependencies. In other words, it becomes much more complicated for someone to add JavaFX depending plug-ins once we remove JavaFX from the local update site.

And, as I noted, that is both good and bad. ;)

Kind regards,
Marcus

-----Ursprungligt meddelande-----
Från: jmc-dev <jmc-dev-bounces at openjdk.java.net> För Mario Torre
Skickat: den 28 augusti 2019 14:17
Till: jmc-dev at openjdk.java.net
Ämne: Re: Sv: RFR: JMC-6555 Convert JOverflow plugin to SWT

On 28/08/2019 13:24, Marcus Hirt wrote:
> Hi all,
> 
> Regarding the removal of the JavaFX bundles, I'll simply note that Oracle has a JavaFX based plug-in for Coherence. Removing the third-party JavaFX bundling from the p2 site would make it much harder to have JavaFX based plug-ins in most versions of JMC (except Oracle's, who would likely override stuff to retain this capability). This is not necessarily a bad thing - harmonizing around SWT (and Swing for some drawing on the AWT_SWT bridge) would simplify many things. Other things would OTOH become much harder. For example, I once prototyped a rather nice 3D heap region and occupancy viewer using JavaFX.

Shouldn't this be treated as any other dependency however? If a plugin needs it, it will just add it to its own p2 configuration, like it's already the case, or am I missing something?

I think it's a good idea to cleanup the dependency set and remove what is not needed. If there's some plugin that gets promoted into core we can always re-add the deps.

Cheers,
Mario

--
Mario Torre
Associate Manager, Software Engineering
Red Hat GmbH <https://www.redhat.com>
9704 A60C B4BE A8B8 0F30  9205 5D7E 4952 3F65 7898