Run idea on the new 1.5beta2 JRE

Hi everybody! I'd really like to try to run idea on the new 1.5 jre, and see how it works... I tried replacing the shipped jre with new 1.5 one, but it seems it does some version checking, and it won't start; is there a way to bypass that?

Thanks!

18 comments
Comment actions Permalink

I think JetBrains should be even more daring; run it on the beta 3! Available under the snapshots link...

Best regards,
Lars Ugleberg

0
Comment actions Permalink

ubik wrote:

it does some version checking, and it won't start; is there a way to bypass that?


Yes: add this to the startup options:

-Didea.no.jdk.check=true

CU,
Edwin

0
Comment actions Permalink

"Lars Ugleberg" <lars.ugleberg@essnet.se> wrote in message
news:8578493.1090743670803.JavaMail.itn@is.intellij.net...

I think JetBrains should be even more daring; run it on the beta 3!

Available under the snapshots link...
>

Have you tried Idea under beta3? I'd be interested in knowing how well it
runs.

Regards,

Glen



0
Comment actions Permalink

No issues here. Pretty fast too. And I love the "-Dswing.aatext=true" flag ;)

0
Comment actions Permalink

ubik wrote:

Hi everybody! I'd really like to try to run idea on the new 1.5 jre, and see how it works... I tried replacing the shipped jre with new 1.5 one, but it seems it does some version checking, and it won't start; is there a way to bypass that?

Thanks!


Just a 1000th warning about this thing. Please do not even think to reports any issues when running under JRE other
than provided one. Thanks for understanding.

--
Maxim Shafirov
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Comment actions Permalink

There are a couple of issues with IDEA under JDK 1.5:

1. Many dialogs (the ones with JTables in them) throw a NullPointerException when shown. This is a known behavior change in 1.5 (when you set a table model, it's asked imediately, even if the table is not visible). By the way, any chance that the JetBrainers could make this small fix?

2. You can't debug applications. The JVM complains that there are no connectors loaded.

0
Comment actions Permalink

Marcus Brito wrote:
> By the way, any chance that the JetBrainers could make this small fix?
No. See my earlier post in this thread.

--
Maxim Shafirov
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Comment actions Permalink

SUN, HELLOW?!

OK, very thanks.

0
Comment actions Permalink

What about debugging?
Personally I don’t buy the Idea’s position of ignoring the JDK1.5 bugs, they would need to fix them anyway sooner or later. Eclipse and other IDEs seamlessly run under JDK 1.5.
On the other hand it is not up to me to decide.

0
Comment actions Permalink

Maxim, be happy you had three whole hours before someone ignored your request!

0
Comment actions Permalink

Point taken ;)

0
Comment actions Permalink

What is this flag for?

0
Comment actions Permalink

2. You can't debug applications. The JVM complains that there are no

connectors loaded.

Well that one's pretty much a showstopper. :)

-- Glen


0
Comment actions Permalink

It turns antialiasing on for all text, unless you have specifically passed an antialiasing hint. It pretty much makes any swing app out there look cool ;)

0
Comment actions Permalink

Hi,

Debug runs fine here....

0
Comment actions Permalink

are you starting the app from within idea debugger or are you trying to attach to a remote process?

Attaching does not work for me with the "no connectors error".

0
Comment actions Permalink

1. Many dialogs (the ones with JTables in them) throw
a NullPointerException when shown. This is a known
behavior change in 1.5 (when you set a table model,
it's asked imediately, even if the table is not
visible).


I have a binary patch for this. Currently it only fixes "move (static) member" dialog. "Web" pane in "Paths" dialog has no that problem in lastest build. If anybody interested, look at http://chmmr.narod.ru/java/idea/

2. You can't debug applications. The JVM complains
that there are no connectors loaded.


This probably can be fixed too. Just classes was moved/renamed in 1.5.

0
Comment actions Permalink

confirm - there is no problem with debugging under beta3.

I've checked what was the difference beetween beta2 and beta3 - looks like a mistake from Sun. There where using the system classloader, that is not applicable for complicated applications which play with that...

0

Please sign in to leave a comment.