The specification version for 9.1 updates

[David DeHaven]

It's impacting deployment. JNLP treats versioned java/j2se tags with no href attributes as Java specification versions so matching on specification is behaving badly at the moment.

-DrD-

> Hi Daniil,
> 
> glad to see that somebody else it at least realizing this problem :)
> 
> I'm assigned to this bug. I have a webrev out for review since April
> [1]. Last time I pinged the mailing list was in June [2].
> Unfortunately nobody seems to be interested in fixing this.
> 
> I think my proposed fix (see
> http://cr.openjdk.java.net/~simonis/webrevs/2016/8149519/) is trivial
> and straightforward so I don't understand what's the problem with it.
> 
> Regards,
> Volker
> 
> [1] http://mail.openjdk.java.net/pipermail/verona-dev/2016-April/thread.html#393
> [2] http://mail.openjdk.java.net/pipermail/verona-dev/2016-June/000420.html
> 
> 
> On Thu, Jul 21, 2016 at 8:23 PM, Iris Clark <iris.clark at oracle.com> wrote:
>> Hi, Daniil.
>> 
>> You're observing the following bug:
>> 
>>    8149519: Investigate implementation of java.specification.verison
>>    https://bugs.openjdk.java.net/browse/JDK-8149519
>> 
>> (The summary should probably be changed to more accurately describe the problem.)
>> 
>> I'm trying to get back to this bug, but the key point is that value of this system property is determined by JCP activity (e.g. a Maintenance Release), not the version of the JDK.
>> 
>>> Am I right that the specification version for 9.1 should still be 9?
>> 
>> Yes.  The value will remain "9" at least until the first MR for JSR 379 (Java SE 9 Release Contents).
>> 
>> Thanks,
>> iris
>> 
>> -----Original Message-----
>> From: Daniil Titov
>> Sent: Thursday, July 21, 2016 9:39 AM
>> To: verona-dev at openjdk.java.net
>> Subject: The specification version for 9.1 updates
>> 
>> Hello,
>> 
>> 
>> 
>> Per http://openjdk.java.net/jeps/223 "The major version number, incremented for a major release that contains significant new features as specified in a new edition of the Java SE Platform Specification"  so $MINOR should not be part of the specification version.
>> 
>> 
>> 
>> At the same time trying the build 9.1.1 (produced with following additional arguments passed to configure:
>> 
>> "--with-version-pre= --with-version-major=9 --with-version-minor=1 --with-version-security=1 --with-version-opt=") and dumping system properties shows that "java.specification.version = 9.1.1" while "java.vm.specification.version = 9"
>> 
>> 
>> 
>> Am I right that the specification version for 9.1 should still be 9?
>> 
>> 
>> 
>> Thanks!
>> 
>> 
>> 
>> Best regards,
>> 
>> Daniil
>> 
>>