I have files loaded from a CVS filesystem, and when I hit Execute (F6) while
my changes are not saved, the editor will not save the file, thus it gets not
compiled and the old class file is executed.
This happens with Dev Build 66 and up, as well as with 3.1 build 5
I test it in #75 build and it works fine.
Be sure, that you don't have mounted a file of the same name twice. That may
cause, that the IDE is trying so save the second file (which is saved, so
>>Be sure, that you don't have mounted a file of the same name twice
I'm sure of that...
I'm using the CVS filesystem thoug. Does that influence the behaviour?
Ctrl-F6 seems to save the file before executing, whereas F6 doesn't
I just tried the following with 31.beta Build 16 and it still doesn't save
Situation: Editor window completely closed
Select a source file (with a main method)
Choose CVS/Edititing/Edit from the context menu
Doubleclick on the file to open the editor
--> File is executed but not saved before
The class files are not inside the same directory structure as the source files!
Well I just tested it with 3.2 build 5 and I still have that problem.
Mount a CVS file system (not the new JavaCVS)
Make sure you check out files read only.
Open a file.
Issue the CVS/Edit command for that file
Edit something inside the file (do not save!)
Press Shift-F6 to execute the project, the file will not be saved
(maybe it has something to do with the read only flag?)
From Product settings I suppose this belongs to core. I am settings Assigned to
filed to reflect this. If I am wrong, change it.
This is still an issue with 3.2 build 32. This also happens with files
from a CVS file system where the option "Check out files readonly" is
As I have said before: this only happens when executing the project, not when
executing a class with a main method directly (via Build/Execute or F6) in that
case the file is saved and compiled properly.
I think this is a major issue! This should get a higher priority (a colleague of
mine just spent several minutes on this because his changes were not working and
it turned out that the reason was that the file was not saved and compiled
before runnnig the project...)
So, after a small investigation I found following behaviour (the relation to the
cvs is irelevant, the behaviour is global):
When you create some project that contains several source files, delegate a main
class and work on it (it means you have opened more files in the editor and some
are changed). Then note that, when project main class is unmodified while some
others are and you execute project (Ctrl+Shift+F6) the modified sources are not
saved and recompiled! Moreover when you clean the project and then exetcute it,
it is not rebuild and CNF is thrown.
Workaround is: before execution explicitly rebuild the project. So increasing
priority to P2, because the project execution does not work properly even the
simple workaround exists. If you think that impact is smaller than P2 then
please decrease, but I think that this should be fixed in 3.2 FCS.
Changing priority to P1. Should be really fixed in 3.2 FCS.
I have prepared a fix. I will commit it to the trunk and the release32 ASAP. It
is just partial rollback of #9931.
Fixed to the trunk.
Fixed to the release32 branch.
NB3.2 build #36
Target milestone -> 3.2
Resolved for 3.4.x or earlier, no new info since then -> closing.