RFR 8208183: update HSDIS plugin license to UPL

[Aleksey Shipilev]

On 08/21/2018 12:14 PM, Magnus Ihse Bursie wrote:
>> Yes, please. And it would be absolutely fantastic to actually build it and ship it in default
>> OpenJDK images :)
> 
> Am I correct in understanding that there are no more legal barriers towards doing such a thing anymore?
> 
> I can easily add a new make target to build hsdis.
> 
> Adding a new binary to the OpenJDK images will require a CSR. This in turn will likely require that
> there are proper tests that can be run (I have no idea of the current status of hsdis testing). I
> can't help you with either of these two.

I wonder if CSR is required only for new enabled-by-default binaries?

There are different degrees of convenience. Having it built and shipped by default would be the most
convenient. Having the configure/build option to include hsdis into image, not enabled by default,
is fine too, as we can enable it for our builds. Having the separate build target is also fine, as
we can add the post-build shell command to copy it in place.

Let's do whatever is simpler from those options.

Thanks,
-Aleksey


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20180821/3289ef50/signature.asc>