Adding JDK6 on OSX
For those with the right NDAs and so on, has anyone managed to do this on OSX? With the latest EAP, I'm unable to click on the 'add JSDK' button, but works if I hit 'enter' instead. Adding the JDK doesnt work, it looks like its added, but going back to the JDK list doesnt show it.
Please sign in to leave a comment.
Hello Hani,
Fixed.
Sorry for inconvenience.
Thank you.
-
Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"
P.S. We are going to release new EAP today.
Excellent, thank you!
Hello Anna,
what exactly is fixed? Ability to click on 'add JSDK' by mouse or JDKs
saving problems?
7041 - is very unstable in that area. Right click on a module->settings
- gives exception. JDKs are not saved always, but only first time. And
other things (or perhaps, most of them caused by not saving JDK info).
-sergiy
Anna Kozlova wrote:
>> For those with the right NDAs and so on, has anyone managed to do this
>> on OSX? With the latest EAP, I'm unable to click on the 'add JSDK'
>> button, but works if I hit 'enter' instead. Adding the JDK doesnt
>> work, it looks like its added, but going back to the JDK list doesnt
>> show it.
>>
Hello Sergiy,
Unfortunately Project Structure has state "work in progress". It means that
it is not polished yet. Now we do not know about major issues with saving
or editing but there are a lot of small UI glitches, focus problems etc
Sorry for inconvenience
Thank you.
-
Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"
>> Hello Hani,
>>
>> Fixed.
>>
>> Sorry for inconvenience.
>>
>> Thank you.
>>
>> -
>> Anna Kozlova
>> JetBrains Inc.
>> http://www.intellij.com
>> "Develop with pleasure!"
>> P.S. We are going to release new EAP today.
>>
>>> For those with the right NDAs and so on, has anyone managed to do
>>> this on OSX? With the latest EAP, I'm unable to click on the 'add
>>> JSDK' button, but works if I hit 'enter' instead. Adding the JDK
>>> doesnt work, it looks like its added, but going back to the JDK list
>>> doesnt show it.
>>>
With all due respect for Hani, who certainly is a prominent personality, I feel kind of depressing that a bug reported by him in order to use an unreleased jdk is fixed in a hour, while I've been manually copying files for weeks every time I compile my GWT app because this bug ( http://www.jetbrains.net/jira/browse/IDEADEV-13420 ) is not being addressed
Uhm, you dont think the fact that maybe 2% of IDEA users use GWT, and 100% add JDKs has anything to do with it?
What I know is I'm stuck with a heap of near-blocking bugs, and no one apparently addressing them. I doubt you were unable to work, because of your JDK issue (except if mac os forces you to use a single java version for all the system, but then apple users themselves are to blame for choosing such a platform!).
Well, now that's just asking for trouble. I'll get the popcorn.
Surely I could apply the same argument to you, and say that you have yourself to blame for choosing such a half baked random web dev framework for production work? Or how about blaming you for using an EAP then whining that it has bugs?
Besides, from what I gather, the JDK issue affects everyone, not just OSX users.
Of course you could, but as you know GWT is actually quite cool (although actually half-baked, unfortunately), so it would not be a very effective argument. I take it that mac os actually forces you to use a single JVM? Poor chap.
And here you force me to state the obvious, but I'm happy to have the opportunity to help you understand: "I'm not whining about the bugs, but the fact that it is a pretty big malfunctioning, that is open since january, that makes the entire experience a pain in the ass and so on..."
And since I'm in a mellow mood I will add another obvious fact, that is: the EAP is as important to me (in that I can use new features before they are released) as it is to jetbrains (in that it helps them give a better shape to the product and fix bugs early).
GWT is a niche framework? Maybe, but I'm not the one that added production support to it in Idea 6, so if jetbrains want to retire support they can declare it, and I will move on. But until they don't, I think the poor souls using GWT with an EAP deserve some respect, and having a bug like that one open for more than 6 months is not respectful.
I know, I realized after posting. Just revert to the friggin' 7020 (as I did, since 7041 was not usable) and do not invade my GWT-bug-fixing steps!
Consider this a generic rant about the slowness the GWT support is evolving these days, and the general close-ness and slugginess of the entire EAP process these days.
It is also not true.
The forcing you to use a single JDK version part not the blame part.