WTF?

Pallade supports code editing for jdk1.5, but doesn't run with 1.5.

Alexander wrote:

>Pallade supports code editing for jdk1.5, but doesn't run with 1.5.

>
Well, IDEA has always shiped with its own JVM - using other ones was
always a "hack", I'm sure once JDK5 is OUT they'll update, maybe for IDEA 5.

Pallade supports code editing for jdk1.5, but doesn't
run with 1.5.

Unofficially it does. So far this is the only drawback I've encountered after starting to run Pallada with 1.5 few weeks ago.

H> Unofficially it does. So far this is the only drawback I've
H> encountered after starting to run Pallada with 1.5 few weeks ago.
H>

And have you noticed any benefits running under 1.5? Is it worth the try?

Thx,
Andrei

I was hoping to be able to the CDS (Class Data Sharing) and see how it affects the run-time memory when I am running smartcvs, idea, and tomcat all under 1.5, but with the debugger not being able to connect, it's a big enough deal for me at this point.

And have you noticed any benefits running under 1.5?
Is it worth the try?

Thx,
Andrei

Well, I'm running all the other java apps under 1.5 too (DBVisualizer, jEdit, the programs we're developing + some other occasional tools) and they all start faster, probably because of the data sharing. I don't know about memory usage but the Pallada doesn't freeze anymore (project size >1500 classes) and JVM options:

-Xms64m -Xmx64m -Xverify:none -Dsun.java2d.noddraw=true -Djars.nocopy=true -Didea.no.jdk.check=true.

I'm also running with windows VM disabled and 512MB seems to go pretty far with these settings.

Does it work if you choose socket transport in Debugger Settings?

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

"Hezekiel" <tilaus@almasoftware.com> wrote in message news:31806339.1094407854145.JavaMail.itn@is.intellij.net...

I'm using build 2239 and JDK1.5.0 RC. All is nice and dandy but no matter what debug or compiler settings I use IDEA reports that

it cannot find
>

com.sun.tools.jdi.SharedMemoryTransport

>

and thus cannot start the debugger. Reason: there's no such class in JDK 1.5.0! There's a SharedMemoryTransportService among other

things. Am I the first one to notice this bug? Isn't anybody else using 2239 with 1.5.0? Isn't Pallada supposed to work with 1.5.0?

No. I tried using the socket transport and could not get it to work. I am using the same setting as what we normally use for the 1.4.x. I get the message that no suitable connector found.

http://www.intellij.net/forums/thread.jsp?forum=22&thread=99453

Does it work if you choose socket transport in
Debugger Settings?

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

The socket transport class name is also changed in 1.5. I don't know if these new classes are downwards compatible, but if they are it wouldn't be a huge task to adapt Pallada to support 1.5 debugging.

Please, could you at least look at the issue?

I don't know about memory usage but the Pallada doesn't freeze anymore

..And with that I didn't mean total freeze (Pallada hasn't done that to me) but the GC seems to be smoother on 1.5.

Since the 1.5 final will ship before the end of the year, do you intend to support 1.5 debugging by then on Pallada or will it take Irida to use that feature?

I wouldn't mind upgrading as long as the upgrade price isn't too high ;)