On 10/17/07, Knut Anders Hatlen <[EMAIL PROTECTED]> wrote: > Jørgen Løland <[EMAIL PROTECTED]> writes: > > > Myrna van Lunteren wrote: > >> Hi, > >> > >> Now that we switched to jdk15 as the base level for the trunk, I see a > >> ton of deprecation warnings. > >> My jdk is: Sun's 1.5.0_12-b04, and I've got build.compiler set to modern > >> > >> I find it bothersome and hard to see 'real' build failures like this, > >> but trunk/tools/ant/properties/modern.properties has deprecation set > >> to 'on'. > >> Would it be reasonable to set this to 'off' or am I the only one > >> seeing these warnings? > >> Or is there another trick I need to do? > >> > >> Thx, > >> Myrna > >> > > > > Wouldn't it be even better if we fixed these? There is usually a good > > reason for deprecating methods, e.g. performance. > > I agree. There may be cases where we want to use deprecated methods, > like in tests of JDBC methods that have been deprecated in later > versions of the spec, but then we could narrow it down to a smaller > number of files for which deprecation warnings are turned off. > > -- > Knut Anders > I think possibly a lot of the warnings I see are indeed connected to valid use of deprecated methods - e.g. PreparedStatement.s/getUnicodeStream... But I logged DERBY-3132.
Myrna
