658 is unusable
I get internal errors when i try to click the Project Settings or IDE
Settings buttons on the menu bar .. enclosed.
Attachment(s):
idea.log
Please sign in to leave a comment.
Attachment(s):
idea.log
the same thing happens to me
Attachment(s):
idea.log
I can't use 658 at all for this same reason.
Do I have to attach my log file??
"Brandon" <bvallade@epoll.com> wrote in message
news:8319594.1034284046807.JavaMail.jrun@is.intellij.net...
Yup.. same problem here.
--
Conor
"Lenny Karpel" <lkarpel@eloquent.com> wrote in message
news:ao4o48$jfl$2@is.intellij.net...
>
>
>
+1
Exactly the same for me...
Same problem for me
Attachment(s):
idea.log
same to above!~
+1
"Lenny Karpel" <lkarpel@eloquent.com> wrote in message
news:ao4o48$jfl$2@is.intellij.net...
>
>
>
Same here too, I'd say this was pretty conclusive -- you might want to pull
the plug on the downloads, or else there's going to be an awful lot of
these..
--
Richard Osbaldeston
(http://www.osbald.co.uk)
Same problem here.
Let's stick to #657.
Guillaume
We are currently investigating the problem and will provide the new build
asap.
Until then the links on the site will be changed back to 657.
Sorry for inconvenience.
--
Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"
"Lenny Karpel" <lkarpel@eloquent.com> wrote in message
news:ao4o48$jfl$2@is.intellij.net...
>
>
>
In fact I'm going back to #655 because #657 with its integrated JRE was quite unusable for me too (no Javadoc and all the other annoyances).
I cannot believe that they are going to deliver this mess as a final release. Do they really expect their customers to tweak around with the startupfile just to make all the goodies work, that worked by default in all the builds up to #655?
Michael Jaeger wrote:
> In fact I'm going back to .. because ..all the other annoyances).
Does it mean that
you can't get no satisfaction?
Sorry, couldn't resist
I tried, though :)
Alain
work, ...
Yes, that was my first impression, too.
Since #657 IDEA's JRE is configured as the default JDK, named "1.4.1",
which is in fact isn't a real JDK (missing javadoc generator, etc).
But then I found out that you just need to configure and use a real JDK in
Project Properties and name it "1.4.1". From then on, the supplied JRE only
serves as IDEA's runtime environment. Any other needed component is used
from the configured JDK.
Maybe this is not optimal, but at least more convenient than having to tweak
startup files.
Sascha
This really should be cross-posted in the "Announcements (EAP)" forum. That is where I always go for information on the latest build.
If there is a reason that people shouldn't use a build that was previously released, you should make an announcement that informs everyone - not just those following this particular thread.
You're right, I was to rude, sorry for that.
But that is just because Idea is such a good IDE that I can't believe that they are doing their product such a harm ;) just a few days before releasing the new version. Why that?
If this is doing the trick, thanks for the tip!
I'll check it out later today (maybe there'll be a fixed #658 until then? ;)).
Michael
I always thougth Intellij guys were a XP shop, but I guess these guys don't write any unit tests or even test the basic functionality like Project Properties before they release a build.
Do not be so rude against the intellij developers!!!
Their IDEA is the absolute top. Be forgiving for an occasional erroneous build.
Johan Wester
There is nothing to forgive - we're all human, mistakes happen. IDEA is a great tool, and so far we've all been using the early-release without any real problems. That we've got this far without a cock-up is a testament to the skill of the IDEA team.
--Bryan
I agree!
+1
Eugene's post is definitely an announcement
I agree too, but...
...657 was a diplomatic cock-up and 658 a technical disaster. Having been able to walk on water in the past it looks like the boys (and girls) at IntelliJ could do to sit back and take a breath. The pressures of hitting a release dead-line appears to have knocked them off their otherwise impeccable stride.
Vince.
Daya,
In fact the problem was in build process not in the code (IDEA was built
without -source 1.4 option).
--
Best regards,
Mike Aizatsky.
-
JetBrains, Inc / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"
Mike Aizatsky wrote:
Mmmm ... don't you have your testsuite running automatically along with
the build with something like cruisecontrol / anthill ?
Edo
Yes we have cruisecontrol set up. But our shipping-version build is slightly
different.
--
Best regards,
Mike Aizatsky.
-
JetBrains, Inc / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"
Hmm, when we will be able to get the bug fixes from build 658? Eugene
Z. said, that you will "provide the new build asap".
Now it looks that you continue in fixing bugs. That is a good
intention, but I believe, it would be better, if we could confirm,
that nothing was broken with fixing bugs in 658.
Tom
On Mon, 14 Oct 2002 14:39:27 +0400, "Mike Aizatsky"
<mike@intellij.com> wrote:
Mike Aizatsky wrote:
we have an installer too ;-(
Edo
Thomas,
#659 is currently in the process of building. If everything goes OK you'll
get the build today.
--
Best regards,
Mike Aizatsky.
-
JetBrains, Inc / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"
We'll deliver the build really asap :-). Unfortunately, investigating javac
1.4 bug mentioned by Mike took a while.
--
Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"
"Thomas Singer" <idea@regnis.de> wrote in message
news:3daaa0fc.14513719@news.intellij.net...
>
>
>
>
>
>