Isn't 1.4 binary compatibility, not enough. Then we can develop, build in 1.5,
but unit/integration test in all the required environments.
There are useful features in 1.5 like templating which give compile time type
checking and eliminate the need to have those costly, ugly type checking
("instance of") all over the place.
Developers should have the discipline to not to used 1.5 specific APIs.
Setting the binary compatibility to 1.4 should take care of that.
Regards,
Sanjaya
On Tuesday 27 February 2007 20:03, Rajith Attapattu wrote:
> Sorry I have no objection to make it 1.4 compatible.
> It's just that I coded it that way, no particular reason :)
> Just get rid of the 1.5 specific details and it would be fine.
>
> Regards,
>
> Rajith
>
> On 2/27/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
> > Sanjiva Weerawarana wrote:
> > >> Rajith, is there anything preventing us from removing/changing these
> > >> parts. I think making this JDK 1.4 compatible will be quite useful.
> > >
> > > I'd say its critical. There are MANY production places which are still
> > > on 1.4 and are unlikely to move any time soon.
> >
> > +1 wherever possible. In a year or so this may change as 1.6 picks up
> > and 1.5 goes mainstream, but for now 1.4 is still huge.
> >
> > --Glen
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
--
Senior Software Architect
WSO2 Inc.
==================================================
“Opportunity is missed by most people because it is dressed in overalls and
looks like work.”
- Thomas Edison
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
