Skip to main content

Any plans to move to JDK 1.6?

4 replies [Last post]
mefoster
Offline
Joined: 2008-11-24
Points: 0

In LoginService.java, one of the imports is:

import org.jdesktop.swingworker.SwingWorker;

This is necessary for JDK 1.5 and less, but in 1.6 SwingWorker is actually included in the JDK itself so the import can be replaced with:

import javax.swing.SwingWorker;

and the external dependency on SwingWorker doesn't need to be there.

The reason I'm pointing this out: I'm working on packaging SwingX for Fedora (it's a dependency of some other packages I want to get in), and I made the above change to make it compile with JDK 1.6 without the external dependency. I just wanted to find out: are you likely to move to 1.6 any time soon (with its included SwingWorker), or should I just keep applying the above patch (not a problem, but I need to know the plans).

Thanks,

MEF

Message was edited by: mefoster

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
rah003
Offline
Joined: 2004-05-26
Points: 0

Plan is to stop active support for Java 5 as soon as SwingX 1.0 is out. We will branch the code base at this point and main branch will be made Java 6+ compatible only. Now the issue is that we have still quite few things we want to solve before releasing 1.0 (check https://swingx.dev.java.net/issues for details) so there is no definitive date for the release set yet ... if you feel like fixing some of the issues, we would be more then happy to get your contribution.
BTW, old swingworker is packaged in extra jar that is part of our distribution so you can just include that jar in a classpath and don't need to apply patches to source.

mefoster
Offline
Joined: 2008-11-24
Points: 0

> BTW, old swingworker is packaged in extra jar that is
> part of our distribution so you can just include that
> jar in a classpath and don't need to apply patches to
> source.

Yes, I noticed that, but unfortunately using privately-packaged libraries like that like that is explicitly not allowed in Fedora. I'll keep applying my source patch for now and look forward to the 1.0 release. :)

Thanks for the quick reply!

rah003
Offline
Joined: 2004-05-26
Points: 0

Not really a privately packaged. There is a project at swingworker.dev.java.net from which the jar comes, we just re-distribute it. Swingworker is also deployed in central maven repo.
Since swingworker and swingx have both same licensing, I don't see a reason why you should not be able to deploy siwngworker along with swingx. Am I missing something?
Cheers,
Jan

mefoster
Offline
Joined: 2008-11-24
Points: 0

Yes, that's also a possibility: I'd have to create a package for swingworker too, and then swingx would depend on it. Which I would normally have done (and in fact did start to do), except that I noticed that swingworker had actually become a part of the official JDK as of 1.6 so I decided to take the lazy route and patch swingx instead. :)