Java-Gaming.org Hi !
Featured games (90)
games approved by the League of Dukes
Games in Showcase (775)
Games in Android Showcase (230)
games submitted by our members
Games in WIP (856)
games currently in development
News: Read the Java Gaming Resources, or peek at the official Java tutorials
 
    Home     Help   Search   Login   Register   
Pages: [1]
  ignore  |  Print  
  JDK 1.4.2?  (Read 6136 times)
0 Members and 1 Guest are viewing this topic.
Offline Dae

Senior Newbie





« Posted 2007-05-27 02:29:01 »

Download links broken Sad Anyone know a mirror?

http://java.sun.com/j2se/1.4.2/download-netbeans.html

Thanks
Offline sma

Junior Devvie





« Reply #1 - Posted 2007-05-27 15:22:57 »

Why do you want to download a 6+ years old JDK with an IDE that is probably of the same age? For development I'd recommend the latest SDK version 6u1 and the latest Netbeans IDE (6.0M9) or Eclipse (3.3RC1) or IDEA (7M1). If you want for some reason to test against that ancient version, use the JRE. Please notice that the JRE version bundled with Netbeans isn't the latest patch level and it might be vulnerable. I wouldn't recommend to install it.

You could download Netbeans and the SDK separately.

.: Truth Until Paradox!
Offline Dae

Senior Newbie





« Reply #2 - Posted 2007-05-27 15:43:38 »

Why do you want to download a 6+ years old JDK with an IDE that is probably of the same age? For development I'd recommend the latest SDK version 6u1 and the latest Netbeans IDE (6.0M9) or Eclipse (3.3RC1) or IDEA (7M1). If you want for some reason to test against that ancient version, use the JRE. Please notice that the JRE version bundled with Netbeans isn't the latest patch level and it might be vulnerable. I wouldn't recommend to install it.

You could download Netbeans and the SDK separately.

I want to create applets compatible with 1.4.2. Can I use the newest NetBeans/SDK and specify the applet is for 1.4.2, or do I have to use an old NetBeans/SDK designed for 1.4.2? Thanks.

At any rate, the downloads are still down.
Games published by our own members! Check 'em out!
Legends of Yore - The Casual Retro Roguelike
Offline sma

Junior Devvie





« Reply #3 - Posted 2007-05-27 16:20:41 »

When compiling your Java code, you can specify the target version. So, you can use Java 6 to develop applets compatible with 1.4.2 if you are careful and if you don't use API calls that are marked with "@since 1.5" or "@since 1.6". Intellij IDEA automatically raises warnings in such cases but I think other Java IDEs aren't clever enough.

You can even develop using the syntax introduced with Java 5 and then use Retrotranslator to fix the class files.

I'd however go for Java 6 (preferable Consumer JRE edition) and hope that by the time I'm ready, there are enough users that have the current Java version installed. According to Adobe (who publishes distribution statistics for Flash - 98% overall, 85% latest version)) 85% of all browsers have Java installed but they don't tell you the version. AFAIK there are no other statistics available from Sun.

.: Truth Until Paradox!
Offline Dae

Senior Newbie





« Reply #4 - Posted 2007-05-27 16:50:19 »

When compiling your Java code, you can specify the target version. So, you can use Java 6 to develop applets compatible with 1.4.2 if you are careful and if you don't use API calls that are marked with "@since 1.5" or "@since 1.6". Intellij IDEA automatically raises warnings in such cases but I think other Java IDEs aren't clever enough.

You can even develop using the syntax introduced with Java 5 and then use Retrotranslator to fix the class files.

I'd however go for Java 6 (preferable Consumer JRE edition) and hope that by the time I'm ready, there are enough users that have the current Java version installed. According to Adobe (who publishes distribution statistics for Flash - 98% overall, 85% latest version)) 85% of all browsers have Java installed but they don't tell you the version. AFAIK there are no other statistics available from Sun.

Thank you very much, sma! That was very informative, and I didn't even think of that. You're right, I should go for Java 6 and hope by the time I'm ready most people have upgraded. Smiley

Offline ryanm

Senior Devvie


Projects: 1
Exp: 15 years


Used to be bleb


« Reply #5 - Posted 2007-05-27 18:52:06 »

When compiling your Java code, you can specify the target version. So, you can use Java 6 to develop applets compatible with 1.4.2 if you are careful and if you don't use API calls that are marked with "@since 1.5" or "@since 1.6". Intellij IDEA automatically raises warnings in such cases but I think other Java IDEs aren't clever enough.

You can certainly do this with Eclipse. The Java/Compiler preference pane allows a compiler compliance level to be specified (1.3, 1.4, 5.0 or 6.0). You can also set it on a per-project basis (Right click on project, Properties/Java Compiler)

The autocomplete will not offer classes and methods that do not exist in the specified version, in addition to the expected "class not found errors" that you get if you go ahead and try and use them anyway.
Offline princec

« JGO Spiffy Duke »


Medals: 1059
Projects: 3
Exp: 20 years


Eh? Who? What? ... Me?


« Reply #6 - Posted 2007-05-28 11:59:23 »

Can you get Eclipse to warn about using libs that are declared @since some version after you've set compatibility to? Would like this feature because I've tripped over it a few times (as I compile for 1.4 but using 6.0)

Cas Smiley

Offline ryanm

Senior Devvie


Projects: 1
Exp: 15 years


Used to be bleb


« Reply #7 - Posted 2007-05-28 14:46:01 »

Hmmm, I may have spoken too soon. Just tried to use System.nanoTime() in a project set to 1.3 source compatibility, and no errors were raised.  Embarrassed

Move along now, nothing to see here...
Offline blahblahblahh

JGO Coder


Medals: 1


http://t-machine.org


« Reply #8 - Posted 2007-05-29 12:46:21 »

Hmmm, I may have spoken too soon. Just tried to use System.nanoTime() in a project set to 1.3 source compatibility, and no errors were raised.  Embarrassed

Move along now, nothing to see here...

Hmm. Did you also set it to *compile* to 1.3?

I only ask because I'm sure I've seen the exact behaviour you described from eclipse (refusing to autocomplete things, but also doing it's little error/warning squiggles under things that were @since the later stuff), so I'm wondering if it's a minor quirk of the proejct settings in your case?

malloc will be first against the wall when the revolution comes...
Offline ryanm

Senior Devvie


Projects: 1
Exp: 15 years


Used to be bleb


« Reply #9 - Posted 2007-05-30 11:44:03 »

I think I did. Had another go and the .settings/org.eclipse.jdt.core.prefs for the project looks like this

1  
2  
3  
4  
5  
6  
7  
8  
9  
10  
11  
12  
#Wed May 30 12:41:26 BST 2007
eclipse.preferences.version=1
org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled
org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.1
org.eclipse.jdt.core.compiler.codegen.unusedLocal=optimize out
org.eclipse.jdt.core.compiler.compliance=1.3
org.eclipse.jdt.core.compiler.debug.lineNumber=generate
org.eclipse.jdt.core.compiler.debug.localVariable=generate
org.eclipse.jdt.core.compiler.debug.sourceFile=generate
org.eclipse.jdt.core.compiler.problem.assertIdentifier=ignore
org.eclipse.jdt.core.compiler.problem.enumIdentifier=ignore
org.eclipse.jdt.core.compiler.source=1.3


Have I missed something?
Games published by our own members! Check 'em out!
Legends of Yore - The Casual Retro Roguelike
Offline erikd

JGO Ninja


Medals: 16
Projects: 4
Exp: 14 years


Maximumisness


« Reply #10 - Posted 2007-05-30 12:04:52 »

Can you get Eclipse to warn about using libs that are declared @since some version after you've set compatibility to? Would like this feature because I've tripped over it a few times (as I compile for 1.4 but using 6.0)

Cas Smiley

Can't you just reference the 1.4 JRE system library in your project's Java Build Path -> Libraries ?

Offline ryanm

Senior Devvie


Projects: 1
Exp: 15 years


Used to be bleb


« Reply #11 - Posted 2007-05-30 13:45:37 »

Yeah, that's the proper way to do it.
It'd just be nice not have to bother having multiple JDKs. All the information needed is there in the form of @since tags, Eclipse just needs to take notice.
Offline Linuxhippy

Senior Devvie


Medals: 1


Java games rock!


« Reply #12 - Posted 2007-05-30 20:42:42 »

Yeah, that's the proper way to do it.
It'd just be nice not have to bother having multiple JDKs. All the information needed is there in the form of @since tags, Eclipse just needs to take notice.

Well the since-tags are missing very often :-/

lg Clemens
Offline princec

« JGO Spiffy Duke »


Medals: 1059
Projects: 3
Exp: 20 years


Eh? Who? What? ... Me?


« Reply #13 - Posted 2007-05-30 22:07:55 »

About time they ran a little tool on their JDKs and automated the generation of @since tags isn't it...

Cas Smiley

Offline Mr_Light

Senior Devvie


Medals: 1


shiny.


« Reply #14 - Posted 2007-05-31 07:46:36 »

aren't since tags Object level annotations?

i.e. wouldn't you still be able to use methods which where introduced later? (provided the class was introduced earlier) 

It's harder to read code than to write it. - it's even harder to write readable code.

The gospel of brother Riven: "The guarantee that all bugs are in *your* code is worth gold." Amen brother a-m-e-n.
Offline princec

« JGO Spiffy Duke »


Medals: 1059
Projects: 3
Exp: 20 years


Eh? Who? What? ... Me?


« Reply #15 - Posted 2007-05-31 10:16:22 »

Nah, just Javadoc annotations I thought. Maybe that's the problem. But then, Eclipse manages to pick up deprecated tags OK.

Cas Smiley

Offline erikd

JGO Ninja


Medals: 16
Projects: 4
Exp: 14 years


Maximumisness


« Reply #16 - Posted 2007-05-31 11:21:45 »

fwiw, I wouldn't trust my work's compatibility to (optional) javadoc tags and the IDE's ability to somehow behave consistently with those, and I'll just keep having multiple JDK's on my system and have eclipse point to the targetted JDK. I have to test on the targetted JRE anyway and as a developer I think having multiple JDK's on my system just 'comes with the territory'.
An added plus is that I'm also sure the JRE javadoc is from the version I'm targetting, so I'll prevent possible confusion there too.

Pages: [1]
  ignore  |  Print  
 
 

 
hadezbladez (1 views)
2018-11-16 13:41:33

hadezbladez (1 views)
2018-11-16 13:35:35

hadezbladez (1 views)
2018-11-16 13:32:03

EgonOlsen (1877 views)
2018-06-10 19:43:48

EgonOlsen (1901 views)
2018-06-10 19:43:44

EgonOlsen (1258 views)
2018-06-10 19:43:20

DesertCoockie (1704 views)
2018-05-13 18:23:11

nelsongames (1389 views)
2018-04-24 18:15:36

nelsongames (2003 views)
2018-04-24 18:14:32

ivj94 (2753 views)
2018-03-24 14:47:39
Deployment and Packaging
by mudlee
2018-08-22 18:09:50

Java Gaming Resources
by gouessej
2018-08-22 08:19:41

Deployment and Packaging
by gouessej
2018-08-22 08:04:08

Deployment and Packaging
by gouessej
2018-08-22 08:03:45

Deployment and Packaging
by philfrei
2018-08-20 02:33:38

Deployment and Packaging
by philfrei
2018-08-20 02:29:55

Deployment and Packaging
by philfrei
2018-08-19 23:56:20

Deployment and Packaging
by philfrei
2018-08-19 23:54:46
java-gaming.org is not responsible for the content posted by its members, including references to external websites, and other references that may or may not have a relation with our primarily gaming and game production oriented community. inquiries and complaints can be sent via email to the info‑account of the company managing the website of java‑gaming.org
Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines | Managed by Enhanced Four Valid XHTML 1.0! Valid CSS!