4 comments

You don't say why it's unusable...it would be for me if I didn't use an external "Makefile" (from a 1.3.1 JDK, no less) to build.

The reason it would be unusable for me is that, all of a sudden, it doesn't seem to like import java.lang.*, or similar import statements, making all of my uses of Java builtin classes invalid. I don't have the patience to go through alt-Entering each error-line.

0

I've posted several bugs. I'm getting lots of asserts opening files, etc.
However, I just deleted my cache and Local VCS files and it's working much
better. It seems that these are easily corrupted with the EAP builds.

--
Jordan Zimmerman
Altura International
Catalog City


0

i have similar problems with java.lang imports. clearing caches only fixes them temporarily. they come right back. bummer. waiting for next build (or workaround)?

0

Likewise. First it wasn't correctly finding references to classes such as
String and was telling me that the import java.lang.* line was unused, but
it still gets errors during ant builds (of course this same bug is in 3.0.3
as well so I'm still using 3.0.1 for daily use).

Guy

"Danny van der Rijn" <dannyv@tibco.com> wrote in message
news:2813395.1049995266684.JavaMail.jrun@is.intellij.net...

i have similar problems with java.lang imports. clearing caches only

fixes them temporarily. they come right back. bummer. waiting for next
build (or workaround)?


0

Please sign in to leave a comment.