Request to remove the --allow-script-in-comments flag which was added to the standard doclet in 1.8.0_121

Peter A peter.abeles at gmail.com
Wed May 31 14:09:14 UTC 2017


Hi dalibor,

The link you provided just describes the new behavior, but no justification
is given for the change.   It cites JDK-8138725 which is not public.  So
it's a bit opaque and hard to tell if the cure is worse than the disease.

Cheers,
- Peter

P.S.  Apologies for having this discussion here.  As suggested, I did join
and send a message to javadoc-dev but it appears that my message was not
approved.

On Wed, May 31, 2017 at 3:16 AM, dalibor topic <dalibor.topic at oracle.com>
wrote:

> On 18.05.2017 17:03, Peter A wrote:
>
>> The general consensus is
>> that it appears to be some sort of security enhancement by forcing people
>> to explicitly allow JavaScript when it's added to javadoc.
>>
>
> Please see http://www.oracle.com/technetwork/java/javase/8u121-relnotes
> -3315208.html for a description of the --allow-script-in-comments option
> for javadoc.
>
> cheers,
> dalibor topic
>
> --
> <http://www.oracle.com> Dalibor Topic | Principal Product Manager
> Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
> <tel:+491737185961>
>
> ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg
>
> ORACLE Deutschland B.V. & Co. KG
> Hauptverwaltung: Riesstr. 25, D-80992 München
> Registergericht: Amtsgericht München, HRA 95603
>
> Komplementärin: ORACLE Deutschland Verwaltung B.V.
> Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
> Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
> Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
>
> <http://www.oracle.com/commitment> Oracle is committed to developing
> practices and products that help protect the environment
>



-- 
"Now, now my good man, this is no time for making enemies."    — Voltaire
(1694-1778), on his deathbed in response to a priest asking that he
renounce Satan.


More information about the adoption-discuss mailing list