ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 2665] - Deprecation warnings are swallowed
Date Thu, 19 Jul 2001 07:33:10 GMT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2665

*** shadow/2665	Wed Jul 18 16:40:06 2001
--- shadow/2665.tmp.21820	Thu Jul 19 00:33:10 2001
***************
*** 42,45 ****
  
  ------- Additional Comments From robert.watkins@qsipayments.com  2001-07-18 16:40 -------
  You could always structure your build so that the classes declaring the 
! deprecation are built seperately from the classes that use the deprecation.
--- 42,57 ----
  
  ------- Additional Comments From robert.watkins@qsipayments.com  2001-07-18 16:40 -------
  You could always structure your build so that the classes declaring the 
! deprecation are built seperately from the classes that use the deprecation.
! 
! ------- Additional Comments From omeyer@i3.informatik.rwth-aachen.de  2001-07-19 00:33 -------
! But I do not know, which classes (or even methodds) are deprecated, as other
! people in the development process deprecate them. 
! 
! What do you have in mind? Moving the classes to a specific folder, that is build
! first? How do I do that with a single method? 
! 
! Do the complete dependency check and then order the classes according to
! deprecation within them? Does not sound feasible to me.
! 
! If you have votes left, think about voting for jdc RFE: 4216683

Mime
View raw message