jdk 1.3 dependencies

[Bill Haneman <Bi...@ireland.sun.com>]

Hi Guys:

In building the current CVS packages I encountered a number of
jdk1.3 dependencies.  Of course I can use 1.3, and am using it
now, but I am not sure that we want to require users of batik
to upgrade from 1.2.X...

I found and removed a couple of dependencies during the hackathon,
but the ones I found today are less trivial to remove:

    *   constructor JMenuItem(Action) [ since 1.3 ]

    *   method java.awt.image.ColorModel.getTransferType()
      [javadoc does not indicate that this is a new method, but it is].
	


I think it should be possible to eliminate these two dependencies,
but it was not so trivial that I felt OK about doing it myself
without raising the question.  

If we absolutely must have 1.3, so be it, but my own preference is to 
hold off on such dependencies as long as we can.

Other opinions?

-Bill

------
Bill Haneman
Ireland Desktop Engineering
Sun Microsystems Ireland Ltd.

jdk 1.3 dependencies

[Thomas E Deweese <th...@kodak.com>]

>>>>> "BH" == Bill Haneman <Bi...@ireland.sun.com> writes:

BH> Hi Guys: In building the current CVS packages I encountered a
BH> number of jdk1.3 dependencies.  Of course I can use 1.3, and am
BH> using it now, but I am not sure that we want to require users of
BH> batik to upgrade from 1.2.X...

    I tend to agree that 1.3 dependencies are probably not warranted
at this point.  In fact this is a larger issue for me since jdk1.3
currently isn't supported on Solaris 2.5.1 (and probably never will
be).  Currently I'm "borrowing" a test solaris 2.7 box for this work.

BH> I found and removed a couple of dependencies during the hackathon,
BH> but the ones I found today are less trivial to remove:

BH>     * constructor JMenuItem(Action) [ since 1.3 ]

    There doesn't appear to be a real nice solution for this one.  I
personally think Action's are great so I kind of hate to replace this
with the alternative but we could.

BH>     * method java.awt.image.ColorModel.getTransferType() [javadoc
BH> does not indicate that this is a new method, but it is].
	
    This can be replaced by checking the SampleModel & datatype in use.

Re: jdk 1.3 dependencies

[Vincent Hardy <vi...@eng.sun.com>]

Bill Haneman wrote:
> 
>> If we absolutely must have 1.3, so be it, but my own preference is to
> hold off on such dependencies as long as we can.
> 
> Other opinions?

I also vote for removing 1.3 dependencies wherever possible.
V.

Re: jdk 1.3 dependencies

[Christophe Jolif <cj...@ilog.fr>]

Bill Haneman wrote:

> If we absolutely must have 1.3, so be it, but my own preference is to
> hold off on such dependencies as long as we can.
> 
> Other opinions?

Yes, in my opinion, we must avoid 1.3 dependencies. Several platforms
have only betas of 1.3 RTE (HP) or even are still on 1.2 RTE (Apple).

-- 
Christophe