Build 6808: feedback request Follow
Selena build 6808, released today, is most likely one of the last EAP builds
before the Milestone 1 release, which we're going to announce and promote
for the general public. We will very much appreciate the help of the EAP
members in testing this build, to ensure that the Milestone 1 release is
stable and usable for day-to-day development work.
Please post your feedback in this thread, or file JIRA requests as usual.
Thanks in advance for your help!
"Develop with Pleasure!"
Please sign in to leave a comment.
Dmitry Jemerov napisa?(a):
If I understand your idea correctly, you want to release some kind-of Idea 7.0 public beta
to the wider audience - allowing for wider and better feedback.
One question: knowing that, will Milestone 1 work with existing Idea 6.0 licenses?
On 2007-04-06 22:40:07 +0400, Michal Szklanowski
Spring facet users will likely run into IDEA-12278
I didn't check the latest EAP - but the release before still had those
problems with the inspection configurations...
Please fix this asap. This can't be so difficult...
Dmitry Jemerov wrote:
Not so much feedback as a question: has the problem with multi-core analyses been fixed in this release. If not, any idea on when it might be fixed, or how close are you guys to resolving it? Did you get a response from Apple? Thanks, Nick.
IMHO this is a blocker: http://www.jetbrains.net/jira/browse/IDEA-12279
By the way: is it intentional that the Weblogic EJB editor isn't shown anymore?
They are fixed in 6808. Sorry for inconvenience.
"Develop with pleasure!"
>> Hello everyone,
>> Selena build 6808, released today, is most likely one of the last EAP
>> builds before the Milestone 1 release, which we're going to announce
>> and promote for the general public. We will very much appreciate the
>> help of the EAP members in testing this build, to ensure that the
>> Milestone 1 release is stable and usable for day-to-day development
>> Please post your feedback in this thread, or file JIRA requests as
>> Thanks in advance for your help!
On 2007-04-07 14:51:54 +0400, Nick Atkins <firstname.lastname@example.org> said:
We had to disable multicore processing on Macs so far.
Great to hear that!
Anna Kozlova wrote:
>> I didn't check the latest EAP - but the release before still had those
>> problems with the inspection configurations...
>> Please fix this asap. This can't be so difficult...
>> Johannes Schneider
>> Dmitry Jemerov wrote:
>>> Hello everyone,
>>> Selena build 6808, released today, is most likely one of the last EAP
>>> builds before the Milestone 1 release, which we're going to announce
>>> and promote for the general public. We will very much appreciate the
>>> help of the EAP members in testing this build, to ensure that the
>>> Milestone 1 release is stable and usable for day-to-day development
>>> Please post your feedback in this thread, or file JIRA requests as
>>> Thanks in advance for your help!
Selena is currently quite unusable for VSS users. File status detection
is very unreliable.
Usually i repeatedly double click the "read-only" status button to try
and make Idea recognize modified files.
Due to this problem I have already forgotten to commit part of the changed
files (and broke the build) twice.
Plus I think I already complained about wrong file status after "commit" with
"keep checked out" option set - but can't find a specific issue for that.
Dmitry Jemerov wrote:
This is a bad one too: http://www.jetbrains.net/jira/browse/IDEA-12284
It is! Any steps to reproduce?
SF> Due to this problem I have already forgotten to commit part of the
SF> changed files (and broke the build) twice.
SF> Plus I think I already complained about wrong file status after
SF> "commit" with "keep checked out" option set - but can't find a specific
issue for that.
IDEA-11708 is fixed - there was a bug in the general synchronization mechanism
Concerning the IDEA-11754 ("Psychedelic colors...") - I never managed to
reproduce that. The option "Keep affected files checked out" also works here.
I suggest to perform the same log-exchage steps after official M1 - it might
be some minority issue which can be fixed to M1 update. Necessary logging
facilities will be included today, so nearest EAP build will be ready for
analysis. Is that suitable for you?
Michael Gerasimov wrote:
Sure. Thanks a lot for all the improvements.
I'll get back to you with any problems in the next eap build ;)
I hope you will do some performance analysis and hopefully some dramatic boosts, since the current eap is really sluggish. It's almost like working with eclipse. Press something, wait.. type something, wait..
It's my fault. I was expecting the editor to appear on the EJB module. The editor for the EJB itself appears as usual.
But: The EJB module editor can be invoked by double clicking on the EJB module node in project view. But when double clicking on an EJB node the respective editor isn't shown but the EJB node is collapsed/expanded. Somewhat inconsistent. And invoking 'Jump to Source' seems an awkward wording to open an editor which isn't related to a specific source file.
...and it isn't fixed yet! In both 6813 and 6905 the problem still exists. So please reopen the bug.
Why don't you make a performance snapshot to let us see what's going on?
We don't see any sluggishness here.
See IDEA-11775, it has snapshots attached and I can create more if you want me too.
Editing has become a little better in the latest builds, but still feels slower than in 6.0.5. Performance drops significantly when opening more than one project at the same time. In that case, editing in one project seems to start analysis in all open projects.
The Changes window's Committed tab still doesn't work for me. When using a date filter to include only stuff since yesterday morning, it processes for a few minutes and then blows up with an error (which I've just reported for build 6808):
Regardless of this error, the processing time required for this feature makes it significantly less useful than the old TMate product.
Idea never did work well with multiple open projects. Usually I have three separate installs of Idea, so I can work with that many projects simultaneously without those modality isusses, wrong project window popping to front, performance problems, ...
What I still don't like is the waste of space.
Currently, when debugging there occurs one tab showing the name of the debugged configuration which also is shown in the title of the debug view (with the iconify, detach and hide buttons). The space right beside that tab is wasted (my debug view is at the bottom). Suggestion: don't show single tabs, but only when more than one components are added to the view.
Force yourself to use a small screen, e.g. 1024x768, maybe then you will feel a need for a change.
Thanks for listening,
Here is a screenshot trying to illustrate to problem: The gray area at the bottom right beside
- the Watches button,
- the Tomcat tab and
- the 5: Debug button
is completely lost.
I agree. I made more detailed comments in the thread at http://intellij.net/forums/thread.jspa?threadID=266733&tstart=0
I can't second your opinion. Most of the time I have at least two
projects open simultaneously, sometimes even three or four. And I don't
see any problems with that, given that I didn't forget to adjust the
memory settings in idea.exe.vmoptions... :)
Stephen Friedrich wrote:
I agree about the "waste of space" argument, but I don't really have a better idea. It is indeed a great improvements to be able to see watches and variables at the same time.
However the icon for "restore layout" is inacceptable. I want my martian back!!!
http://www.jetbrains.net/jira/browse/IDEADEV-15752 is pretty bad as well. I
don't think it's a good idea to release M1 with a high potential of deadlocking
when a user just starts it for the first time...
+10 I get this constantly, which is a pain when I'm trying to develop a
Sascha Weinreuter wrote: