I'm aware it'll need a license for the distributor just like HISE, but what's the interaction with HISE?
I don't want to derail that thread to become a JUCE 8 discussion (so if there is a demand for talking about it let's move it to a separate thread), but long story short:
their attempt to crack down on a vaguely described illegitimate use case causes any platform that provides the ability to create program logic to consider every contributor as a JUCE developer. So if you have a setup where a few people were working on a HISE project, you might end up requiring a license seat for each developer, regardless of whether he is actually using JUCE (= compiling the plugin) or just working on graphics or anything else that is not "close to the metal". This in combination with the increased pricing for each seat can lead up to license cost increases of 500% - 1000% in the worst case setup (which would be a team of 5 developers working with HISE with a single JUCE 6 / 7 license).
I know of a few project team setups which are using HISE and are negatively affected by this change so I've decided to hold off updating to JUCE 8 unless there is a really game-breaking issue. There are a few nice things in JUCE 8 like the monitor-refresh rate synced animation framework and the new Direct 2D renderer, but none of those justify that legal fiasco.