Woot FINALLY! Build #3378, Cannot open projects AT ALL!

It can't get anything but better now.

I installed build 3378 on OSX 10.4.1 with Java.1.4.2 and no matter what UI piece I use to try to open a project, they simply will not open at all. If you'd like me to capture what this looks like in a video I can, but I can describe it.

"Open Recent Projects->Select project name"

Back at the same screen I was at before.

6 comments
Comment actions Permalink

here something that IntelliJ spit out...


Error during dispatching of java.awt.event.InvocationEvent[INVOCATION_DEFAULT,runnable=com.apple.eawt.Application$4@afd566,notifier=null,catchExceptions=false,when=1119388087486] on apple.awt.CToolkit@e31e74: java.lang.String.contains(Ljava/lang/CharSequence;)Z
java.lang.NoSuchMethodError: java.lang.String.contains(Ljava/lang/CharSequence;)Z
at com.intellij.openapi.vfs.VirtualFile.skipUTF8BOM(VirtualFile.java:421)
at com.intellij.openapi.vfs.VirtualFile.getReader(VirtualFile.java:388)
at com.intellij.openapi.vfs.VirtualFile.getReader(VirtualFile.java:355)
at com.intellij.openapi.fileEditor.impl.LoadTextUtil.loadText(LoadTextUtil.java:11)
at com.intellij.openapi.project.impl.BaseFileConfigurable.a(BaseFileConfigurable.java:109)
at com.intellij.openapi.project.impl.BaseFileConfigurable.loadSavedConfiguration(BaseFileConfigurable.java:30)
at com.intellij.openapi.project.impl.ProjectManagerImpl.loadProject(ProjectManagerImpl.java:127)
at com.intellij.ide.impl.ProjectUtil.openProject(ProjectUtil.java:43)
at com.intellij.ide.MacOSApplicationProvider$Worker$1.handleOpenFile(MacOSApplicationProvider.java:12)
at com.apple.eawt.Application$4.run(Application.java:353)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:102)
at com.intellij.ide.IdeEventQueue.a(IdeEventQueue.java:162)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:104)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:234)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:178)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:170)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)



Here's hoping I can open this projects in the latest official release.

0
Comment actions Permalink

It seems that you're having the same issue Brad mentioned this morning.

String.contains() is new to JDK 5.0. Try running IDEA on a 5.0 JDK.

Vince.


0
Comment actions Permalink

Edit the Info.plist file to specify 1.5, I don't know why IDEA ships with 1.4 when it's such a blatant lie. FYI this breakage has been there since the second EAP build that supported 1.5.

0
Comment actions Permalink

Fixed.
We are really in bad need for an inspection for use of 1.5 API in our
project...

Eugene.

"Gregory Pierce" <no_mail@jetbrains.com> wrote in message
news:18119312.1119388199637.JavaMail.itn@is.intellij.net...

It can't get anything but better now.

>

I installed build 3378 on OSX 10.4.1 with Java.1.4.2 and no matter what UI
piece I use to try to open a project, they simply will not open at all. If
you'd like me to capture what this looks like in a video I can, but I can
describe it.

>

"Open Recent Projects->Select project name"

>

Back at the same screen I was at before.



0
Comment actions Permalink

Yeah! I think a lot of people would benefit from such an inspection!

0
Comment actions Permalink

You shouldn't need an inspection for that, as long as you're compiling with the right jdk version. It looks like IDEA code is retroweaved, however. Retrowever has an option to check all class references are valid, ensuring you're not using any new API's inadvertently -- you just need to provide the full project classpath.

If IDEA is going down this road, I suggest to go all the way to full retroweaver integration (not that hard to do, I think):

1) Automatically retroweave classes after they're compiled
2) Automatically check class references against the 'target' JDK

0

Please sign in to leave a comment.