RFR: 8199871: Deprecate pack200 and unpack200 tools

[Alex Buckley]

The warning message gives us just enough room to expand on the terse and 
still-new-to-most-people phrase "deprecated for removal". Using the 
phrase "planned to be removed" is desirable, because it gives a tiny bit 
more wriggle room than "will be removed". So, I propose this for warnings:

   The THING is deprecated, and is planned for removal in a future JDK 
release.

And for `jar --help-extra`:  (-n is like an API element, so the d-f-r 
phrase is OK)

   -n, --normalize      (Deprecated for removal) Normalize information
                        in the new jar archive after creation

Also, since JEP 336 is now proposed to target JDK 11, I think it's OK to 
add `since="11"` to the annotation in class Pack200.

Alex

On 6/11/2018 10:19 AM, Henry Jen wrote:
> Sounds good to me. If no objections, I’ll change this for pack200 and unpack200 as well.
>
> Cheers,
> Henry
>
>> On Jun 11, 2018, at 9:07 AM, Paul Sandoz <paul.sandoz at oracle.com> wrote:
>>
>> Hi Henry,
>>
>> I am unsure if the warning messages are copying a pattern of previous warning messages for other for removal deprecations but i would like to suggest some stronger language e.g.:
>>
>>   Warning: The {0} option is deprecated for removal and will be removed in a future JDK release\n
>>
>> Thoughts?
>>
>> Paul.
>>
>>> On Jun 8, 2018, at 6:56 PM, Henry Jen <henry.jen at oracle.com> wrote:
>>>
>>> Hi,
>>>
>>> Please review this webrev[1] in which we mark Pack200 related API and tools deprecate, and print a warning about tools to be remove in a future JDK release. To avoid interrupt existing tools depends on the output, an option is provided to suppress the warning message.
>>>
>>> The option name is following the convention of javah, not the GNU style as we should. The rationale is that this is a temporary option and an existing convention would make it more consistent for users. Anyhow, if we have a strong feeling this should be changed, we can do that.
>>>
>>> For jar tool, the normalize option use Pack200 is also deprecated, the suppress option only available to the new GNU style option mode. As if user need to provide the option, the command line change is necessary, so without compatible mode option should not be an issue.
>>>
>>> Cheers,
>>> Henry
>>>
>>> [1] http://cr.openjdk.java.net/~henryjen/jdk11/8199871/0/webrev/
>>
>