----- Original Message ----- > Hi Kumar, > > On 07/25/2013 07:05 PM, Kumar Srinivasan wrote: > > Changing any of these lines is very painful, because too many > > scripts and tests have made assumptions on these lines, and some of > > these are System properties which are baked at build time. >
People have been building with this fixed since 2007, as have all your proprietary builds. > I am looking at it from the users' point of view. Oracle (proprietary) > JDKs claim to be "java version..." as do IBM (proprietary) JDKs. Isn't > openjdk the odd one out if it claims to be "openjdk version..."? > Yes. > I also think it will be much more painful for all our users to have to > fix their scripts and tests if any of those scripts or tests happen to > rely on the output of "java -version". Fixing our tests and scripts > would surely be less painful. > > Thanks, > Omair > No packages have ever shipped using "openjdk version", which is why I immediately noticed it as a regression. So the discussion is moot really. It's still going to get changed back in local packages. It would just be better to have it fixed upstream. -- Andrew :) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: 248BDC07 (https://keys.indymedia.org/) Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07
