IDEA 6.0 Beta coming: plea for a feedback

Hi All,

we're going to release IDEA 6.0 Beta soon and really need your feedback either
positive and negative.
Feel free to step up with any issues that bother you most in latest EAPs,
we'll consider fixing them as soon as it possible.
Anyway, this will not be a released version of any kind so if we won't
actually fix your favorite pet issue in Beta we still have plenty of time
to fix before it actually goes GA.

Thanks in advace

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


168 comments

hi, Grant Smith

thanks for feedback...

Unfortunately, i can't reproduce this problem. But anyway a new functionality
was added to guarantee the TextEditor tab opened by default

Serega Vasiliev

Overall everything looks pretty good to me. One issue I do have though
is now if you open a JSF page (.jspx) it opens it up in the
"Navigation" tab by default. It should default to the "Text" tab.

Thanks for a great product.



0

hi, Grant Smith

thanks for feedback...

Unfortunately, i can't reproduce this problem. But anyway a new functionality
was added to guarantee the TextEditor tab opened by default

Serega Vasiliev

Overall everything looks pretty good to me. One issue I do have though
is now if you open a JSF page (.jspx) it opens it up in the
"Navigation" tab by default. It should default to the "Text" tab.

Thanks for a great product.



0

Would be great if someone would take a look at:

http://www.jetbrains.net/jira/browse/IDEA-8512

May not seem urgent, but I was doing one of my locally famous IDEA demos when I ran into it ... :)

0

I have a problem with our Ant build scripts that has been around for a long time. There are quite a few JIRA issues which are very similar to it but I thought I'd describe the problem here since it may get some more eyeball time.

We use a slightly customized version of Ant 1.6.2. Basically, it has some extra tasks -- AntContrib and some we wrote for interfacing with our nightly automated build system. The classes for these extra tasks are in two jars in the Ant lib directory. We use taskdefs like this to import the tasks into the build script:

The build script works fine from both the commandline and from IDEA, once IDEA has been configured to run it using our customized version of Ant. However, the elements for the custom tasks (e.g. ]]>) are marked as red: Element 'buildstat' is undefined. So my build file, which works, has red splashed all over it :(

Thanks,
Gordon

0

Done.
http://www.jetbrains.net/jira/browse/IDEA-8545
http://www.jetbrains.net/jira/browse/IDEA-8546

Regards,
Amnon

Dmitry Jemerov wrote:

Hello Amnon,

AG> 1. Our ANT build 'clean' target deletes a directory that is excluded
AG> from the module roots. When I run the 'clean' and then the 'build'
AG> target (I'm sure it is clear what they do :)) the directory is
AG> marked as red (not found?) in Module Roots and even though it exists
AG> (as it's created by 'build') I have to remove it from the excluded
AG> directories on the left and add it again on the right.
AG> AG> 2. In JavaScript, if I use auto completion and instead of pressing
AG> Enter when I have the right choice from the list I press '(' I get
AG> something like: "fun()(|)" where | denotes cursor position. I think
AG> that should be fixed to yield the same result as pressing Enter.

Could you please file JIRA issues for both of these problems?

0

Done.
http://www.jetbrains.net/jira/browse/IDEA-8545
http://www.jetbrains.net/jira/browse/IDEA-8546

Regards,
Amnon

Dmitry Jemerov wrote:

Hello Amnon,

AG> 1. Our ANT build 'clean' target deletes a directory that is excluded
AG> from the module roots. When I run the 'clean' and then the 'build'
AG> target (I'm sure it is clear what they do :)) the directory is
AG> marked as red (not found?) in Module Roots and even though it exists
AG> (as it's created by 'build') I have to remove it from the excluded
AG> directories on the left and add it again on the right.
AG> AG> 2. In JavaScript, if I use auto completion and instead of pressing
AG> Enter when I have the right choice from the list I press '(' I get
AG> something like: "fun()(|)" where | denotes cursor position. I think
AG> that should be fixed to yield the same result as pressing Enter.

Could you please file JIRA issues for both of these problems?

0

What happened to my "File View"? I'm using Source Safe, and "File View" is grayed-out in the menu. Has this been replaced by something else?

0

Hello DaveB,

D> What happened to my "File View"? I'm using Source Safe, and "File
D> View" is grayed-out in the menu. Has this been replaced by something
D> else?

"File View" has always been a CVS only feature.

Try "Changes" view (Alt-9) as a replacement.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0

My pet peeve is that some of the intentions no longer take you to the screen which lets you modify the settings, nor add the "ignore" javadoc to the code.

Also for some reason, every method in our code is being flagged with "Required tag @parm is missing" or "Required tag @return is missing". We usually don't put those in for simple getter/setters or well named parameters. And, there's no way to turn that off in the Errors settings page that I can find. This one will REALLY annoy our developers, as this isn't an issue with IDEA 5, and code that looked clean there will apper to be bad in IDEA 6.

But, the other stuff is looking good...

Douglas Bullard

0

I use tomcat server, remote debug,

software:

java version "1.4.2_08"
xp professional 2002 service pack 2

hardware:
mobile intel 4 - m cpu 2.19ghz
1.0GB
mobility radeon 9000
intel(r) pro/100 ve network connection

debug env:
transport: share memory
debug mode: attach
share memory address: jdbconnepg

tomcat server info:
Server version: Apache Tomcat/5.5.9
Server built: Mar 26 2005 02:21:04
Server number: 5.5.9.0
OS Name: Windows XP
OS Version: 5.1
Architecture: x86
JVM Version: 1.4.2_08-b03
JVM Vendor: Sun Microsystems Inc.

0

+1

I tried to find a way to turn it off on Friday and couldn't find a way.

Douglas Bullard wrote:

My pet peeve is that some of the intentions no longer take you to the screen which lets you modify the settings, nor add the "ignore" javadoc to the code.

>

Also for some reason, every method in our code is being flagged with "Required tag @parm is missing" or "Required tag @return is missing". We usually don't put those in for simple getter/setters or well named parameters. And, there's no way to turn that off in the Errors settings page that I can find. This one will REALLY annoy our developers, as this isn't an issue with IDEA 5, and code that looked clean there will apper to be bad in IDEA 6.

>

But, the other stuff is looking good...

>

Douglas Bullard

0

Hello Douglas, Norris,

What kind of checks do you expect from javadoc inspection?

Thank you.

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

+1

I tried to find a way to turn it off on Friday and couldn't find a
way.

Douglas Bullard wrote:

>> My pet peeve is that some of the intentions no longer take you to the
>> screen which lets you modify the settings, nor add the "ignore"
>> javadoc to the code.
>>
>> Also for some reason, every method in our code is being flagged with
>> "Required tag @parm is missing" or "Required tag @return is missing".
>> We usually don't put those in for simple getter/setters or well named
>> parameters. And, there's no way to turn that off in the Errors
>> settings page that I can find. This one will REALLY annoy our
>> developers, as this isn't an issue with IDEA 5, and code that looked
>> clean there will apper to be bad in IDEA 6.
>>
>> But, the other stuff is looking good...
>>
>> Douglas Bullard
>>


0

Unfortunately I still have this issue with 5581..

0

Hello yerba,

Your problem may be caused by a bug in implementation of "shared memory"
transport.
Try to change transport from "shared memory" to "socket".

I use tomcat server, remote debug,

software:

java version "1.4.2_08"
xp professional 2002 service pack 2
hardware:
mobile intel 4 - m cpu 2.19ghz
1.0GB
mobility radeon 9000
intel(r) pro/100 ve network connection
debug env:
transport: share memory
debug mode: attach
share memory address: jdbconnepg
tomcat server info:
Server version: Apache Tomcat/5.5.9
Server built: Mar 26 2005 02:21:04
Server number: 5.5.9.0
OS Name: Windows XP
OS Version: 5.1
Architecture: x86
JVM Version: 1.4.2_08-b03
JVM Vendor: Sun Microsystems Inc.



0

Ant:

while editing ant file, reference to macro arguments like @ are not autocompleted.
property introduced via <dirname property=.. is not recognized

Project toolwindow: is it so hard to let user assign an icon for every module? I've 100+ modules and reeeally look for a way to (visually) differentiate them!

0

Hi Igor,

The ]]> property is already fixed. As to macrodef params completion,
I'll check this.

Thanks,

--
Best regards,
Vyacheslav Lukianov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"

Ant:

while editing ant file, reference to macro arguments like @ are
not autocompleted. property introduced via <dirname property=.. is not
recognized

Project toolwindow: is it so hard to let user assign an icon for every
module? I've 100+ modules and reeeally look for a way to (visually)
differentiate them!


0

At my company, documenting return values, parameters, etc. on methods is optional if they are well named and obvious (getters and setters are an excellent example). We used to require these per a code tool which generated them, and realized that a large number were unnecessary.

When we do code reviews, we make a note if there are any items which need additional documentation, and it will be fixed.

All we really need is a way to make the currently "required" JavaDoc checks for @param and @return to be optional - give us a way to turn them off. There should be very few inspections which can't be turned off to meet differing code standards.

Thanks,

Douglas Bullard

0

Hello Douglas,

I am sorry but I still don't understand you. Why do you have to keep Javadoc
Inspection 'switch on'? Just remove it from profile and that's all. I mean
that I do not understand what checks from it do you really want in your code?


Thank you.

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

At my company, documenting return values, parameters, etc. on methods
is optional if they are well named and obvious (getters and setters
are an excellent example). We used to require these per a code tool
which generated them, and realized that a large number were
unnecessary.

When we do code reviews, we make a note if there are any items which
need additional documentation, and it will be fixed.

All we really need is a way to make the currently "required" JavaDoc
checks for @param and @return to be optional - give us a way to turn
them off. There should be very few inspections which can't be turned
off to meet differing code standards.

Thanks,

Douglas Bullard



0

Oh, and @throws, too, should be optional...

0

Because I didn't know where it was :)

I assume you're referring to "Declaration has javadoc problems" in the inspection profile. That indeed was the source of my problems. I've adjusted that to suit my preferences.

BTW, the search gadget really helped finding this (OK, I should have used it before, but hey).

Thanks!


Douglas Bullard

0

not this problem, only compile, after update cache, idea dead as mutton, 2014 files in my project

0

Hello Douglas,

Great :)

Thank you.

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

Because I didn't know where it was :)

I assume you're referring to "Declaration has javadoc problems" in the
inspection profile. That indeed was the source of my problems. I've
adjusted that to suit my preferences.

BTW, the search gadget really helped finding this (OK, I should have
used it before, but hey).

Thanks!

Douglas Bullard



0

Hello Dmitry,

I haven't seen the problem yet in 5569.

0

Hello Jari,

JP> SourceSafe check-in does not work on #5561. If I do a 'Compare with
JP> SourceSafe version' it correctly shows differences with the files.
JP> but if I do a File or directory check-in it says 'No changes
JP> detected'.

If the problem still happens with the build 5581, could you please file a
JIRA request?

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Not a major issue but 6.0 Beta doesn't seem to allow the attaching of ant build files unless they have a default target specified in the project tag.

5.1 doesn't have this issue - I had a few legacy projects I was trying out and it took me a little while to find out why they would open in 5.1 and not in 6.0.

0

Hello Dmitry,

I've been using "File View" with Source Safe for quite a long time. I'm looking at it active while I type this. I'll look into the "Changes" view, but something isn't right here...

0

Dear Jari,

JP> SourceSafe check-in does not work on #5561. If I do a 'Compare with
JP> SourceSafe version' it correctly shows differences with the files.
JP> but if I do a File or directory check-in it says 'No changes
JP> detected'.

Could you please specify in a more detail:
1. Do files are correctly coloured - changed with blue, new with green?
2. Is the "Checkin" menu item is available under all conditions?

thank you in advance,

best wishes,
Michael Gerasimov,
JetBrains Omea Developer


0

Well, I have to be honest, I probably will not be purchasing 6.0. I have played with the EAP on and off, but nothing really grabs me this time. There is nothing new that I really need or want.

While all of the big stuff looks great, where I work it does me no good. I go against the grain here by using IDEA(I am supposed to be using WSAD). Like other users here, it is cash out of my pocket to go my own way.

But we are far from the bleeding(heavily hemorrhaging) edge. We still use 1.3 here, though we will soon be blazing forward to 1.4.

For example, collaboration is done through Lotus Notes/Sametime, which we share with our customers; I actually would not want to have to deal with a second type of chat system.

Don’t get me wrong, I like IDEA and I think it makes me productive(it even teaches me something new from time to time).

But, what I have been looking for are the small things. The things I would/do use all the time. The things that set IDEA apart from most of the other IDEs.

Like having the ability to add a date variable for live templates(How hard can that be? You already have line number and package as variables). Plus, the annoyance of not being able to create a template shortcut starting with a ‘/’; well, unless you go in and manually edit the XML files.

If I have JAVA code in a JSP, my JAVA style todos don’t show up. Fortunately, I only have a few JSPs in my project, so I can manually check them before doing a release.

I would still like a small text box next to the find button, I really don’t need or want a pop up box every time I do a simple text search(plus it is nice to have that a visual indicator to remind you want you are searching on, if you get off on a tangent). Good thing I have Ultraedit for doing that type of work.

Then there are the occasional slow downs and the swapping of focus when you have 2 project open.

These are the small things that would make my life easier when coding in IDEA.

I am sure, one day, I will use some of the other stuff(I know I will be grateful when I move up to 1.4).

But, over the last few days(and then some), it is some of the small things I mentioned above that I would like to have seen; the things that would have allowed me to code with pleasure.

Sometimes, it is the small things that count(and can be used) the most.

0

While all of the big stuff looks great, where I work
it does me no good. I go against the grain here by
using IDEA(I am supposed to be using WSAD). Like
other users here, it is cash out of my pocket to go
my own way.


I'm in the same situation here. Everyone else but me is using WSAD. I was hoping to see more features in Demetra that would prompt me to upgrade, but I'm not 100% confident that I will. As you've said, the new teamwork features are amazing, but I can't make full use of them in my environment.

That being said, there are some nice new features that I'd sure take advantage of: the new VCS integrations and enhanced javascript support are on the top of my list. On the other hand, there are some missing features that will make me think twice before upgrading. From the top of my head:

1) True websphere integration. By "true" here, I mean complete enough to make me drop WSAD. If I still have to use WSAD to deploy the application, like I have to now, the integration is close to useless. Oh, ant scripts won't help either. Generating deployment code using ant every time I change a few classes is -way- to slow for development.

2) More control over what's reported as errors. I've asked many, many times, for a way to disable HTML, or CSS, or Javascript, or whatever, for a whole project. Error reporting and inspections really gets close to useless when you need to ignore most of them.

3) SVK support. This is more of a dream, but something that would make me upgrade instantly :)

That, and the countless bugs fixed. Still thinking...

0

+1billion

I'll probably upgrade out of habit more than anything else, but you are spot on.

0

Please sign in to leave a comment.