[Tm4j-developers] [ tm4j-Bugs-830520 ] TM4J API won't compile cleanly on pre-1.4 JDK versions

[SourceForge.net <no...@so...>]

Bugs item #830520, was opened at 2003-10-26 15:11
Message generated for change (Comment added) made by kal_ahmed
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=391879&aid=830520&group_id=27895

Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Florian G. Haas (haasfg)
Assigned to: Kal Ahmed (kal_ahmed)
Summary: TM4J API won't compile cleanly on pre-1.4 JDK versions

Initial Comment:
I don't recall pre-JDK 1.4 session being officially
dropped for TM4J, but a few classes contain code that
won't compile on JDK 1.3. Specifically, this is related
to "root causes" for exceptions and the String class's
replaceAll() method, both of which were introduced in
JDK 1.4.

There is only one additional invocation in the API
classes that does compile on 1.3, but not 1.2.2, this
being an uncaught IOException in the constructor of
FileOutputStream. So on the whole it shouldn't be
infeasible to extend backwards compatibility, at least
for the basic TM4J API, back to JDK 1.2.2.

Side note: needless to say, compiling on pre-1.4 does
require that the XML-related libraries are available on
the classpath. 

----------------------------------------------------------------------

>Comment By: Kal Ahmed (kal_ahmed)
Date: 2004-02-27 16:33

Message:
Logged In: YES 
user_id=176992

Verified that a build can now be done using JDK 1.3.1

When using JDK 1.3.x the TopicMapDoclet cannot be compiled
as it makes use of features not supported prior to JDK 1.4.
The build.xml files has been updated to make the
TopicMapDoclet optional.

----------------------------------------------------------------------

Comment By: Kal Ahmed (kal_ahmed)
Date: 2004-01-26 16:10

Message:
Logged In: YES 
user_id=176992

Removed most JDK 1.4-specific stuff. But some error handling
for the Ozone backend relies on being able to get at the
"stack" of nested exceptions. I'm not sure if there is a
clean way around this. It might be that TM4J will have to
require JDK1.4 for the Ozone backend.

----------------------------------------------------------------------

Comment By: Florian G. Haas (haasfg)
Date: 2003-10-26 15:16

Message:
Logged In: YES 
user_id=291928

"I don't recall pre-JDK 1.4 session" was of course meant to
be "I don't recall pre-JDK 1.4 support". What was I
thinking? :-)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=391879&aid=830520&group_id=27895