Hi, Volker. >> I've also filed build bug (8162687) referencing 8145919 and 8162686.
> I suppose you wanted to refer to "java.vm.specification.version" in "8162687: ava.specification.version is always set to $MAJOR at build time" because "java.vm.specification.version" is actually being set in the code snippet you reference in the bug. Also, this is done at run-time, during HotSpot initialization and not at build time. > Finally, I think this is more of a HotSpot issue and not a build issue. > > So I've changed the bug accordingly. If you think I've misunderstood > something, please feel free to change it back. The change needs to occur for both java.specification.version and java.vm.specification.version. I suspect that the VM code will depend on how the build change is made, as I've modified the bug to more clearly indicate this and moved it back to build because it's possible that the VM code may set their value from the build implementation. The build team may choose to file a separate bug to handle the VM issue, but ideally they should be handled at the same time. thanks, iris
