Re: [JBoss-dev] build fails strangely with jdk1.4

[Philip V. B. <tb...@fr...>]

When jdk 1.1 was released few developers  used java.
but now it's the most used programming language|vm.
undeprecated changes can have a mayor impact.

removing a method out of some class isn't the same as
adding a new keyword.
(Why not System.assert() )

I can live with changes like assert,
(althru i haven't called any method assert)
but is likely that many ejb's won't work any more due to serialisation
between 2 versions of java.

one must not be backward compatible forever.
but changes should take place at once and as early as possible.

If the next version windows isn't compatible with the current one, then
windows is history.

Greetz-Tbone,



----- Original Message -----
From: "Andreas Schaefer" <an...@jb...>
To: <jbo...@li...>
Sent: Sunday, September 30, 2001 9:25 PM
Subject: Re: [JBoss-dev] build fails strangely with jdk1.4


> I don't think so. Backward compatibility is good for a
> while but have a look at M$ Windows or other OS
> I can become a pain in the a*.
> You can have evolution and backward compatibility over
> a long period but you should give a grace period.
>
> I can't understand that still handleEvent() is still in
> java.awt.Component.
>
> Andy
>
> ----- Original Message -----
> From: "Philip Van Bogaert" <tb...@fr...>
> To: <jbo...@li...>
> Sent: Sunday, September 30, 2001 11:17 AM
> Subject: Re: [JBoss-dev] build fails strangely with jdk1.4
>
>
> > yes, i'am aware,
> > but it seems that migrating from 1.3 to 1.4,
> > wouldn't go that easy as migrating from 1.2 to 1.3
> > (remember 1.0 to 1.1)
> >
> > minus for sun, they claim os independency but
> > they haven't have version indepencency
> >
> > for me backward compatibilty is a mayor issue
> >
> > I'am only thinking in the future
> >
> > Tbone
>
>
>
>
> _______________________________________________
> Jboss-development mailing list
> Jbo...@li...
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>