If IDEA detects the CVS server connection failure, it should display a warning (including "do not display this message in the future"), remember the state and silently fail during the rest of the session. It must be possible to work on CVS projects offline without being driven up the wall by modal CVS error messages.
Ant is not showing targets defined in included build files, which means they ca't be run inside Idea. This used to work in 5.x and needs to be fixed before the 6.0 release.
Parametrized tests are one of the major value adds to JUnit 4. As such, IMHO, one can claim JUnit 4 support without supporting parameterized tests.
IDEA v6 failure to support paramertized tests is even highlighted in the devX article on JUnit4 (http://www.devx.com/Java/Article/31983) which is linked to from the JUnit.org homepage.
The fault was actually my version of TortoiseSVN that modified the working copy in such way that it's not accessible with Subclipse either. Subclipse at least gives a clear message:"svn: This client is too old to work with working copy 'SomeProject'; please get a newer Subversion client ".
>Sometimes when committing/updating from another program >(TortoiseSVN), IDEA sets the module files as unversioned. >Doing some action on a file after this gives "Error: svn: >xxx is not under version control", although it is.
>The only way to fix this is to checkout the project to a >new, clean directory and configure IDEA to use it.
>I cannot say the problem is in IDEA. Maybe TortoiseSVN >does some non-standard changes to the svn-files.
>If anyone else has this issue I would be happy to hear >from you.
The fault was actually my version of TortoiseSVN that modified the working copy in such way that it's not accessible with Subclipse either. Subclipse at least gives a clear message:"svn: This client is too old to work with working copy 'SomeProject'; please get a newer Subversion client ".
Let me guess: you're using Tortoise's beta version. The beta version uses subversion 1.4, which uses a new working copy format that's not backwards compatible.
PJ> This is definitely an upgrade showstopper for us (working with CVS PJ> offline continuously times out): PJ> PJ> http://www.jetbrains.net/jira/browse/IDEA-9133 PJ> PJ> If IDEA detects the CVS server connection failure, it should display PJ> a warning (including "do not display this message in the future"), PJ> remember the state and silently fail during the rest of the session. PJ> It must be possible to work on CVS projects offline without being PJ> driven up the wall by modal CVS error messages.
The build 5661, released today, contains an initial implementation of CVS offline mode. Could you please try it out, and tell us if it works sufficiently well, or if there are problems remaining?
It's not just project file scanning. For me, even the IDE startup time is very noticeably slower than 5.1.2. As for opening a project, improvements have been made in the latest EAP builds but 5.1.2 is still much quicker on the exact same project.
For 6.0: Time to show splash screen = 25 sec Time till IDE is open at the welcome page = 45 sec Time to open project (show open files) = 150 sec Time for CPU usage to drop back to 0 after opening project = 215 sec
The last time is there because once the project opened, the CPU usage stayed at 100% for another 65 seconds.
For 5.1.2: Time to show splash screen = 10 sec Time till IDE is open at the welcome page = 20 sec Time to open project (show open files) = 120 sec
With 5.1.2, the CPU usage dropped back to 0 immediately after the project opened.
I have recently added a few more plugins loaded for 6.0 (eg Hungry Backspace) compared with 5.1.2 but the issue has been there for a long time before that.
I took a CPU snapshot for the 6.0 project open test. Can I ftp it somewhere?
It is marked as fixed, but it does not work in #5661. Several quick fixes of InspectionGadgets are a bit handicapped by this bug. And I also need it fixed for my update to the Lineage plugin (for easy subclassing).
could the "work offline" setting be maintained when reopening the project (since it blocks for ~30 secs when open the project when I can't route to the server)
JF> could the "work offline" setting be maintained when reopening the JF> project (since it blocks for ~30 secs when open the project when I JF> can't route to the server)
It's of course easy to remember this setting, but is it the right thing to do, or should the problem of initial project opening be solved in some other way? What do others think?
(I'd rather not clutter the Welcome screen with any CVS-related controls, but I can probably make the "Work offline" toggle action available in the main menu when no project is open.)
(I'd rather not clutter the Welcome screen with any CVS-related controls, but I can probably make the "Work offline" toggle action available in the main menu when no project is open.)
An online/offline indicator/toggle action is something that IMO belongs into the status bar. See the screenshot taken from Thunderbird.
>> (I'd rather not clutter the Welcome screen with any CVS-related >> controls, but I can probably make the "Work offline" toggle action >> available in the main menu when no project is open.) >> SW> An online/offline indicator/toggle action is something that IMO SW> belongs into the status bar. See the screenshot taken from SW> Thunderbird.
Currently the offline status is stored per CVS root (assuming that it's not only the client which can be offline but also a particular server), which is not too easy to fit in a single status bar indicator. Is this an over-complication that should be changed to a simple global offline flag?
Currently the offline status is stored per CVS root (assuming that it's not only the client which can be offline but also a particular server), which is not too easy to fit in a single status bar indicator. Is this an over-complication that should be changed to a simple global offline flag?
Ah, that makes sense, but I think that in 95% of the "offline" cases the network cord is unplugged or the company network isn't reachable. Maybe it could be a tri-state icon in the status bar that also indicates the case when just some roots are offline and which has a Hector-like popup menu that allows to toggle the global state as well as the per-root states in case there's a real need for it.
Currently the offline status is stored per CVS root (assuming that it's not only the client which can be offline but also a particular server), which is not too easy to fit in a single status bar indicator. Is this an over-complication that should be changed to a simple global offline flag?
I agree there are actually two situations to cover (general lack of a network connection and unavailability of a specific server) but I agree with Sascha that most of the time it's the former situation that will exist (and, if you only use one VCS server, the latter is effectively the same as the former).
I'd vote for a simple global online/offline flag that all VCS clients should respect. Or perhaps it could be per-project (and stored in the .iws) since I'd imagine most projects are unlikely to have more than one VCS configured.
MS> I'd vote for a simple global online/offline flag that all VCS MS> clients should respect. Or perhaps it could be per-project (and MS> stored in the .iws) since I'd imagine most projects are unlikely to MS> have more than one VCS configured.
Unfortunately I can't promise that offline mode will be supported for any other clients besides CVS in 6.0. (For Perforce, there's already the "Perforce is enabled" flag. For Subversion, this should be much less of an issue because most operations performed by IDEA in background will only touch your local copy. And for StarTeam and VSS... well, we'll see if we can fit it in.)
I'd also vote for a simple global online/offline flag which represents the client state (= network unplugged). The setting should persist over two IDEA working sessions. In my case this would cover 100% of all cases, since I have only one CVS server and I always start with the blank desktop (no automatic open of project).
i vote for the above (starteam) with as many votes as possible... please include support for task pinning otherwise starteam integration is practically useless
http://www.jetbrains.net/jira/browse/IDEA-8362
I really hope project scanng improves before the final release.
for history see:
5646 feedback Project file scanning better - still problematic
http://www.intellij.net/forums/message.jspa?messageID=5152773#5152773
and
5622 feedback Project file scanning still an a big problem
http://www.intellij.net/forums/message.jspa?messageID=5145905#5145905
Reset sticky data (-A) on CVS update doesn't work - http://www.jetbrains.net/jira/browse/IDEA-9015
It's driving me nuts.
ANT Build Jump toSource doesn't work for tasks in imported ant files.
http://www.jetbrains.net/jira/browse/IDEA-8686
This is definitely an upgrade showstopper for us (working with CVS offline continuously times out):
http://www.jetbrains.net/jira/browse/IDEA-9133
If IDEA detects the CVS server connection failure, it should display a warning (including "do not display this message in the future"), remember the state and silently fail during the rest of the session. It must be possible to work on CVS projects offline without being driven up the wall by modal CVS error messages.
Thanks,
Peter
CVS update fails with updating a binary file to a selected version from
the cvs history view:
http://www.jetbrains.net/jira/browse/IDEA-6464
--
Per Thomas
Ant is not showing targets defined in included build files, which means they ca't be run inside Idea. This used to work in 5.x and needs to be fixed before the 6.0 release.
http://www.jetbrains.net/jira/browse/IDEADEV-7613
http://www.jetbrains.net/jira/browse/IDEADEV-2359
IMHO focus loosing problem makes IDEA unusable on Linux
The inability to run JUnit 4.x based Parameterized tests: http://www.jetbrains.net/jira/browse/IDEADEV-7348
Parametrized tests are one of the major value adds to JUnit 4. As such, IMHO, one can claim JUnit 4 support without supporting parameterized tests.
IDEA v6 failure to support paramertized tests is even highlighted in the devX article on JUnit4 (http://www.devx.com/Java/Article/31983) which is linked to from the JUnit.org homepage.
D'oh... Of course I meant to say "...on can not claim JUnit 4 support without supporting parameterized tests".
Why is it you can proofread a post 5 times, and not see a typo like that, and then see it the moment you hit "Post Message"?
The fault was actually my version of TortoiseSVN that modified the working copy in such way that it's not accessible with Subclipse either. Subclipse at least gives a clear message:"svn: This client is too old to work with working copy 'SomeProject'; please get a newer Subversion client ".
>Sometimes when committing/updating from another program >(TortoiseSVN), IDEA sets the module files as unversioned. >Doing some action on a file after this gives "Error: svn: >xxx is not under version control", although it is.
>The only way to fix this is to checkout the project to a >new, clean directory and configure IDEA to use it.
>I cannot say the problem is in IDEA. Maybe TortoiseSVN >does some non-standard changes to the svn-files.
>If anyone else has this issue I would be happy to hear >from you.
Message was edited by:
Sakke Wiik
Are you sure you aren't using Tortoise SVN 1.4?
This has exactly the same symptoms and is caused by the working-copy structure being incompatible between Subversion 1.3 and 1.4.
Hmm and you editted your message before I could reply ;)
Message was edited by:
Simon Knott
Let me guess: you're using Tortoise's beta version. The beta version uses subversion 1.4, which uses a new working copy format that's not backwards compatible.
Oh, vote for http://jetbrains.net/jira/browse/IDEA-9204 if you care :)
Hello Peter,
PJ> This is definitely an upgrade showstopper for us (working with CVS
PJ> offline continuously times out):
PJ>
PJ> http://www.jetbrains.net/jira/browse/IDEA-9133
PJ>
PJ> If IDEA detects the CVS server connection failure, it should display
PJ> a warning (including "do not display this message in the future"),
PJ> remember the state and silently fail during the rest of the session.
PJ> It must be possible to work on CVS projects offline without being
PJ> driven up the wall by modal CVS error messages.
The build 5661, released today, contains an initial implementation of CVS
offline mode. Could you please try it out, and tell us if it works sufficiently
well, or if there are problems remaining?
--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"
It's not just project file scanning. For me, even the IDE startup time is very noticeably slower than 5.1.2. As for opening a project, improvements have been made in the latest EAP builds but 5.1.2 is still much quicker on the exact same project.
That should not happen. Startup is made really faster in 6.0. Could you please take a snaphot of what is going on with your project?
Yes i upgraded to 1.4 and didn't read the fine print (actually there was a big warning) :)
Hi Eugene
I did some measurements.
For 6.0:
Time to show splash screen = 25 sec
Time till IDE is open at the welcome page = 45 sec
Time to open project (show open files) = 150 sec
Time for CPU usage to drop back to 0 after opening project = 215 sec
The last time is there because once the project opened, the CPU usage stayed at 100% for another 65 seconds.
For 5.1.2:
Time to show splash screen = 10 sec
Time till IDE is open at the welcome page = 20 sec
Time to open project (show open files) = 120 sec
With 5.1.2, the CPU usage dropped back to 0 immediately after the project opened.
I have recently added a few more plugins loaded for 6.0 (eg Hungry Backspace) compared with 5.1.2 but the issue has been there for a long time before that.
I took a CPU snapshot for the 6.0 project open test. Can I ftp it somewhere?
Thanks.
http://www.jetbrains.net/jira/browse/IDEADEV-8035
It is marked as fixed, but it does not work in #5661. Several quick
fixes of InspectionGadgets are a bit handicapped by this bug. And I also
need it fixed for my update to the Lineage plugin (for easy subclassing).
Bas
could the "work offline" setting be maintained when reopening the project (since it blocks for ~30 secs when open the project when I can't route to the server)
Hello Josh,
JF> could the "work offline" setting be maintained when reopening the
JF> project (since it blocks for ~30 secs when open the project when I
JF> can't route to the server)
It's of course easy to remember this setting, but is it the right thing to
do, or should the problem of initial project opening be solved in some other
way? What do others think?
(I'd rather not clutter the Welcome screen with any CVS-related controls,
but I can probably make the "Work offline" toggle action available in the
main menu when no project is open.)
--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"
Dmitry Jemerov wrote:
An online/offline indicator/toggle action is something that IMO belongs into the
status bar. See the screenshot taken from Thunderbird.
Sascha
Attachment(s):
offline.PNG
Hello Sascha,
>> (I'd rather not clutter the Welcome screen with any CVS-related
>> controls, but I can probably make the "Work offline" toggle action
>> available in the main menu when no project is open.)
>>
SW> An online/offline indicator/toggle action is something that IMO
SW> belongs into the status bar. See the screenshot taken from
SW> Thunderbird.
Currently the offline status is stored per CVS root (assuming that it's not
only the client which can be offline but also a particular server), which
is not too easy to fit in a single status bar indicator. Is this an over-complication
that should be changed to a simple global offline flag?
--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"
Dmitry Jemerov wrote:
Ah, that makes sense, but I think that in 95% of the "offline" cases the network
cord is unplugged or the company network isn't reachable. Maybe it could be a
tri-state icon in the status bar that also indicates the case when just some
roots are offline and which has a Hector-like popup menu that allows to toggle
the global state as well as the per-root states in case there's a real need for it.
Sascha
Dmitry Jemerov wrote:
I agree there are actually two situations to cover (general lack of a
network connection and unavailability of a specific server) but I agree
with Sascha that most of the time it's the former situation that will
exist (and, if you only use one VCS server, the latter is effectively
the same as the former).
I'd vote for a simple global online/offline flag that all VCS clients
should respect. Or perhaps it could be per-project (and stored in the
.iws) since I'd imagine most projects are unlikely to have more than one
VCS configured.
--
Mark Scott
mark@codebrewer.com
Hello Mark,
MS> I'd vote for a simple global online/offline flag that all VCS
MS> clients should respect. Or perhaps it could be per-project (and
MS> stored in the .iws) since I'd imagine most projects are unlikely to
MS> have more than one VCS configured.
Unfortunately I can't promise that offline mode will be supported for any
other clients besides CVS in 6.0. (For Perforce, there's already the "Perforce
is enabled" flag. For Subversion, this should be much less of an issue because
most operations performed by IDEA in background will only touch your local
copy. And for StarTeam and VSS... well, we'll see if we can fit it in.)
--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"
We really need this. StarTeam support is a show stopper. Thanks!
http://www.jetbrains.net/jira/browse/IDEADEV-1001
Dmitry,
I'd also vote for a simple global online/offline flag which represents the client state (= network unplugged). The setting should persist over two IDEA working sessions. In my case this would cover 100% of all cases, since I have only one CVS server and I always start with the blank desktop (no automatic open of project).
Thanks,
Peter
i vote for the above (starteam) with as many votes as possible... please include support for task pinning otherwise starteam integration is practically useless