On Mon, 25 Nov 2019 at 07:33, Jan Lahoda <[email protected]> wrote: > If you want to add a new constraint that it must be easy to do a build > which includes nb-javac, I have nothing against that, but you may need to > design that yourself (and preferably contribute that back).
I will also need to solve this problem for PraxisLIVE, so definitely motivated to contribute here. As I said when we merged this, though, I think we need a build flag to include the nb-javac and/or JavaFX modules. There is no reason someone building from our sources needs to be restricted by our binary distribution restrictions. Derivatives, distributions and corporate/education deployments could all benefit here. This was potentially easier with the older extra cluster use? On Mon, 25 Nov 2019 at 08:17, Ernie Rael <[email protected]> wrote: > On 11/24/2019 11:32 PM, Jan Lahoda wrote: > > -there is only a single Plugin Portal for all NetBeans 11.0, 11.1 and 11.2; > > .... > One way, > somewhat kludgy, would be to make a clone of the portal for a new > version and allow plugins to be individually added/replaced on an as > need basis. Each version of the IDE has its own plugin portal URL already. It is purely a quirk of the current legacy infrastructure that the same plugin catalog is served to each. The portal will be replaced soon, and AFAIK serving different catalogs to different IDE versions will no longer be an issue - at least I hope that issue is solved in it?! Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
