Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #14321 > unrolled thread

Re: How to turn off those warning messages during ant build?

Back to article view | Back to comp.lang.java.programmer

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: How to turn off those warning messages during ant build? Arne Vajhøj <arne@vajhoej.dk> - 2012-05-05 20:50 -0400
    Re: How to turn off those warning messages during ant build? Gene Wirchenko <genew@ocis.net> - 2012-05-07 09:33 -0700

#14321 — Re: How to turn off those warning messages during ant build?

On 4/15/2012 10:58 PM, Gene Wirchenko wrote:
> On Fri, 13 Apr 2012 21:07:40 -0400, Arne Vajhøj<arne@vajhoej.dk>
> wrote:
>
> [snip]
>
>> Are you claiming that it is poor software architecture/development
>> to write code that does not have a single flaw at time of being written
>> but 5 or 10 years later give warnings or errors with a new Java
>> version?
>
>       I have seen code that worked with one version of a compiler fail
> on the next version, because the parsing had been tightened up.  Code
> that had worked for years would suddenly compile with errors.  This
> was between different versions of Microsoft Visual FoxPro.

That can happen.

But it is not what is happening here.

OP's code was perfectly valid pre-1.5 Java that gives
warnings due to raw types in 1.5+.

Arne

[toc] | [next] | [standalone]

#14362

On Sat, 05 May 2012 20:50:32 -0400, Arne Vajhøj <arne@vajhoej.dk>
wrote:

>On 4/15/2012 10:58 PM, Gene Wirchenko wrote:
>> On Fri, 13 Apr 2012 21:07:40 -0400, Arne Vajhøj<arne@vajhoej.dk>
>> wrote:
>>
>> [snip]
>>
>>> Are you claiming that it is poor software architecture/development
>>> to write code that does not have a single flaw at time of being written
>>> but 5 or 10 years later give warnings or errors with a new Java
>>> version?
>>
>>       I have seen code that worked with one version of a compiler fail
>> on the next version, because the parsing had been tightened up.  Code
>> that had worked for years would suddenly compile with errors.  This
>> was between different versions of Microsoft Visual FoxPro.
>
>That can happen.
>
>But it is not what is happening here.
>
>OP's code was perfectly valid pre-1.5 Java that gives
>warnings due to raw types in 1.5+.

     The Visual FoxPro code in question was perfectly valid by the
rules at the time.  A change in compiler version broke the code.

Sincerely,

Gene Wirchenko

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.java.programmer

csiph-web