File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Java in General and the fly likes Using libraries in an older java version Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


Win a copy of The Mikado Method this week in the Agile and other Processes forum!
JavaRanch » Java Forums » Java » Java in General
Reply Bookmark "Using libraries in an older java version" Watch "Using libraries in an older java version" New topic
Author

Using libraries in an older java version

Carlos A. Perez
Greenhorn

Joined: Apr 09, 2004
Posts: 27
Hi:

Has someone ever imported libraries compiled in for example java 1.3 in a project compiled with 1.2?? did you have any problem? how did you fix it?

In the company i work for is migrating an application from 1.2 to 1.3 but some other applications still will use 1.2 but the import some classes from the aplication migrated to 1.3. I know that is supossed that should be compatibility but mmmm... im not really sure.

Thanks
Campbell Ritchie
Sheriff

Joined: Oct 13, 2005
Posts: 32708
    
    4
You won't be able to get Java 1.3 libraries to work in something you are compiling in Java 1.2, but it should work the other way round.

But why are you using Java 1.3 when Java 6 has been available for 6 months?
Jesper de Jong
Java Cowboy
Bartender

Joined: Aug 16, 2005
Posts: 12929
    
    3

Originally posted by Campbell Ritchie:
But why are you using Java 1.3 when Java 6 has been available for 6 months?

Campbell, in the world of business, companies always want to spend as little money as possible on IT. They don't upgrade their Java version whenever a new version is out, because upgrading costs time and money. Generally companies keep using the software that they have until there is some business reason to replace it by something new. And even when building something new, they'd rather stick with proven technology than with the latest and greatest.

I've just finished a project for one client and I've started on a different project last week. The previous project was Java 1.4, the new project is Java 5. The new project is the first Java 5 project I'm doing for a client. (I've been using Java 5 and 6 for lots of other things, but not for projects for clients yet).


Java Beginners FAQ - JavaRanch SCJP FAQ - The Java Tutorial - Java SE 7 API documentation
Scala Notes - My blog about Scala
Campbell Ritchie
Sheriff

Joined: Oct 13, 2005
Posts: 32708
    
    4
Posted by Jesper Young
spend as little money as possible on IT
Thank you. I can see it would be profitable to be behind the times.

Just like the post yesterday on the beginner's forum about the employer who thought people might not be able to use JavaScript?

If I had to pay for Java myself I wouldn't have upgraded it!
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 35252
    
    7
They don't upgrade their Java version whenever a new version is out, because upgrading costs time and money.

Quite true, especially if the new version doesn't provide many immediately beneficial features.

Still, having a project to move to 1.3 now seems quite odd (it has been EOL'ed). I, too, am curious what the reason for that might be.


Android appsImageJ pluginsJava web charts
 
I agree. Here's the link: http://zeroturnaround.com/jrebel - it saves me about five hours per week
 
subject: Using libraries in an older java version
 
Similar Threads
difference between struts.jar and struts-core.jar
clrscr() function?
Different results on JDK 1.2 and 1.3??
I need help setting the compiler compliance to as earlier a version as is reasonable.
Why can't inner classes declare static members?*