Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Gene Wirchenko Newsgroups: comp.lang.java.programmer Subject: Re: How to turn off those warning messages during ant build? Date: Thu, 12 Apr 2012 19:29:45 -0700 Organization: A noiseless patient Spider Lines: 55 Message-ID: References: <15429764.10.1333589060953.JavaMail.geo-discussion-forums@pbae2> <10168300.3443.1333651355770.JavaMail.geo-discussion-forums@pbcto7> <4f7e2ee4$0$288$14726298@news.sunsite.dk> <4f8772f3$0$285$14726298@news.sunsite.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: mx04.eternal-september.org; posting-host="wKah3EH8kutwAOV6+9FiEQ"; logging-data="28904"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/vgj8H1MvHjDKRFu7PZWS9GU6RvXk1cSg=" X-Newsreader: Forte Agent 4.2/32.1118 Cancel-Lock: sha1:YmQXbdEoxq0n6jStiAgCT0qRJIA= Xref: csiph.com comp.lang.java.programmer:13512 On Thu, 12 Apr 2012 20:27:28 -0400, Arne Vajhøj wrote: >On 4/5/2012 10:35 PM, Gene Wirchenko wrote: >> On Thu, 05 Apr 2012 19:46:39 -0400, Arne Vajhøj >>> It is not technical debt. >>> >>> Technical debt is when the code was not good when written. >> >> I think you are making a useless distinction here. Something got >> changed that caused technical debt. > >Not per standard definitions. > >http://en.wikipedia.org/wiki/Technical_debt In the second to last paragraph, the above has "Activities that might be postponed include ... tackling compiler ... warnings." > >Technical debt (also known as design debt or code debt) is a neologistic >metaphor referring to the eventual consequences of poor software >architecture and software development within a codebase. And changing the compiler is not part of software development? >http://martinfowler.com/bliki/TechnicalDebt.html > > >Technical Debt is a wonderful metaphor developed by Ward Cunningham to >help us think about this problem. In this metaphor, doing things the >quick and dirty way sets us up with a technical debt, which is similar >to a financial debt. > Q&D such as changing compilers without testing everything. >>> Here something externally changed. >> >> Internally, the version of Java used changed. Had that not >> changed, there would be no problem. > >True. > >But upgrading compiler/runtime does not really qualify as >"poor software architecture and software development" or >"quick and dirty way". It sure can. Do you port the code to the new compiler, or do you just hope? Sincerely, Gene Wirchenko