Bundled JRE 1.5 in Iridia

They can't do it until there's JRE 5.0 for OSX, or else they'll have to make their code run on 5.0 and 1.4.2. Currently, running Irida on JRE 5.0 causes lots of problems (with fonts and other things) so they'd have to work those bugs out, but make sure the code still works on 1.4.2.

I'd guess preparing for JRE 5 is a good thing because 5.0 related bugs are at least not introduced with new code, and JB needs to do it nonetheless. Additionally, JRE 5 offers some additional capabilities (debugging, profiling etc.). Strange enough (cannot imagine that JRE 5 is so much faster than 1.4) the Irida EAPs I tried running on JRE 5 (and the ones which worked, at least most functionality) were much smoother to use (editor seems quite slow on some EAP builds, it is ok with 5.0, no idea why).
I understand that 5.0 cannot be the default, but I at least would very much like to see Irida running on JRE 5, so I can replace it "at my own risk". Early EAP builds worked, when I tried running some newer one on 5.0 it threw an exception, haven't tried since then.

regards,

Messi

Hi,

The JRE is replacible at your own risk with additonal VM parameters like:
-XX:MaxDirectMemorySize=384m -XX:MaxPermSize=128m -XX:PermSize=64m
-Didea.no.jdk.check=true

Bernhard Messerer wrote:

I'd guess preparing for JRE 5 is a good thing because 5.0 related bugs are at least not introduced with new code, and JB needs to do it nonetheless. Additionally, JRE 5 offers some additional capabilities (debugging, profiling etc.). Strange enough (cannot imagine that JRE 5 is so much faster than 1.4) the Irida EAPs I tried running on JRE 5 (and the ones which worked, at least most functionality) were much smoother to use (editor seems quite slow on some EAP builds, it is ok with 5.0, no idea why).
I understand that 5.0 cannot be the default, but I at least would very much like to see Irida running on JRE 5, so I can replace it "at my own risk". Early EAP builds worked, when I tried running some newer one on 5.0 it threw an exception, haven't tried since then.

regards,

Messi

--
Maxim Mossienko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Do I need to do anything special to make the debugger and more importantly the remote debugging work?

thanks
vinay

I know I actually can replace the JRE with a 5.0 one (even used a few EAP builds with 5.0), but IDEA doesn't work on it properly, so yes, I risked it and found out it doesn't work ;) - I never got debugging to work correctly and when trying last time with around EAP B#3150 I got an exception at startup (NoClassDef if I remember correctly) that I didn't get with earlier EAPs, so it seems to me code has been added that doesn't work on a 5.0 JVM. This is why I think JB should "sometimes" test on 5.0 and ensure it works, you'll have to do this earlier or later in any case, but "later" means porting, checking and testing more sources.
Sure, its your business so what am I telling you... and sure, an IDE is something different - the incompatibilities and exceptions on 5.0 mainly seem to stem from usage of com.sun.* classes, don't know whether this is necessary when creating an IDE; but I always tested my apps on new releases of the JVM since the earlier I try, the less of pressure and work I have when it really should run there.
One question... I know the idea.no.jdk.check vm param, but what about the memory related XX params you mentioned?

kind regards,

Messi

Hi,

You may need tools.jar from 1.4 if some problems with debugging
transport appears

Vinay Moharil wrote:

Do I need to do anything special to make the debugger and more importantly the remote debugging work?

thanks
vinay

--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

Hi,

When I work on the sources (not regular build) I use JDK1.5 on Windows,
there is another engineer that uses JDK1.5 on Linux. The used JDK for
the IDEA development is still 1.4.

Bernhard Messerer wrote:

I know I actually can replace the JRE with a 5.0 one (even used a few EAP builds with 5.0), but IDEA doesn't work on it properly, so yes, I risked it and found out it doesn't work ;) - I never got debugging to work correctly and when trying last time with around EAP B#3150 I got an exception at startup (NoClassDef if I remember correctly) that I didn't get with earlier EAPs, so it seems to me code has been added that doesn't work on a 5.0 JVM. This is why I think JB should "sometimes" test on 5.0 and ensure it works, you'll have to do this earlier or later in any case, but "later" means porting, checking and testing more sources.
Sure, its your business so what am I telling you... and sure, an IDE is something different - the incompatibilities and exceptions on 5.0 mainly seem to stem from usage of com.sun.* classes, don't know whether this is necessary when creating an IDE; but I always tested my apps on new releases of the JVM since the earlier I try, the less of pressure and work I have when it really should run there.
One question... I know the idea.no.jdk.check vm param, but what about the memory related XX params you mentioned?

They are important when working with large projects, otherwise OOM
errors possible with relatively free heap.

kind regards,

Messi

--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"