Alan, Sorry for not being clean enough.
tl/jdk/make/java/rmi repository produce deprecation warning while compiling and these warning threaten as an error. Therefor build are stopped. I use 1.8.0-ea-b37 for compilation. I workarounded the problem with JAVAC_LINT_OPTIONS but would like to know is it a known issue. -Dmitry On 2012-09-03 22:05, Alan Bateman wrote: > On 03/09/2012 18:42, Dmitry Samersoff wrote: >> Hi Everybody >> >> Q. Is it (below) known problem? >> >> Q. Does it make sense to turn deprecation warning off by default or at >> least add an env variable to control it? >> >> >> ../../../src/share/classes/sun/rmi/server/ActivatableRef.java:311: >> warning: [deprecation] newCall(RemoteObject,Operation[],int,long) in >> RemoteRef has been deprecated >> >> public synchronized RemoteCall newCall(RemoteObject obj, >> >> >> etc. >> >> make[2]: Leaving directory `/home/dms/ESC/JSDP/tl/jdk/make/java/rmi' >> > jdk8/tl is built and tested on all platforms, including boot cycle > builds, every night so it mostly be in a healthy state. That said, there > is currently an issue with OPENJDK=true builds in the corba repository. > It's not an issue when the closed repos are present. Sean Coffey is > currently looking into it. From the fragment in your mail then it > doesn't look like you are running into it. From your mail I can't tell > if you are just observing deprecation warnings or the warnings are fatal > (as part of the ongoing effort to reduce javac warnings then they are > fatal in areas that should be warning free). In any case I would suggest > bringing your issue to core-libs-dev@openjdk. > > -Alan. > -- Dmitry Samersoff Java Hotspot development team, SPB04 * There will come soft rains ...
